You can read this article in Japanese (日本語) | Spanish (español)
Q. What calling scenarios are supported?
A. Dubber records Inbound calls (i.e. An external party calling a RingCentral user), Outbound calls (i.e. a RingCentral user calling an external party) and Internal calls (i.e. a RingCentral user calling another RingCentral user). Inbound calls that result in a voicemail being deposited are not recorded.
Q. Can I disable RingCentral Automatic Call Recording (or change configuration specific for a user/extension)
A. Automatic Call Recording must be enabled on the RingCentral account (and for each user that is to be recorded) for Dubber to ingest recordings.
Q. Users can still delete recordings in RingCentral via the Admin Portal (via Call log). If I delete recordings here, will they be deleted from Dubber?
A. Dubber ingests recordings shortly after they’re captured at the end of the phone call. Deleting a recording from the Call log will not affect Dubber’s automated ingestion of recordings, however it may be best practice to avoid deleting recent recordings where a delay in full processing (by RingCentral or Dubber) may be present.
Q. What happens if I change the password of the user used to associate and authenticate Dubber with my RingCentral account?
A. If the RingCentral administrator’s password is changed, the authentication token used by the Dubber application will be expired. If this occurs, Dubber support will reach out to the impacted user to re-establish authorization. Dubber recommends not using RingCentral’s password expiration feature for this reason.
Please sign in to leave a comment.