RingCentral: Deploying MIRC

 

We will need the most minimal of server built.

You can build a Linux or Windows Server with the minimal recommend hardware resources for each platform.

We will show the steps for Debian Linux and Windows 2019.  You can adjust as necessary for your chosen platform.

Linux

You must be at NodeJS version 10.5 or higher.
On Linux, do NOT make a user called MIRC.  It is a reserved name.  We suggest mirc-admin for a username.

From a command prompt on your Linux server, execute the following commands

•     sudo wget https://apps.bridgeoc.com/mirc/install-debian.sh
•     sudo chmod +x install-debian.sh
•     ./install-debian.sh
•     cd  /home/mirc
•     sudo nano .env

Proceed to Common Config below to gather the bits to populate the .env file

Windows

You will need to install NodeJS.  We recommend using the most current LTS edition (Long Term Support). 
Verify the current version number at  https://nodejs.org.

NodeJS 16.1.1

Download the following zip file and extract into a folder
C:\MIRC

MIRC.zip

From an elevated NodeJS command prompt, execute the following commands.

• c:
• cd  \mirc
• npm install dotenv
• npm install node-windows
• npm install @ringcentral/sdk --save
• npm install @ringcentral/subscriptions --save
• node install-windows
• notepad .env

Proceed to Common Config below to gather the bits to populate the .env file

Common Config

When the hosting server has been installed, you will need to obtain 2 pieces.

1. Your Microsoft Tenant ID, obtained upon authorizing the application
        Authorize the Azure AD application

2. A RingCentral JWT
       Create a RingCentral JWT

    You will need to identify our application in your JWT configuration and allow usage.
        Our application client ID is:  2MxdWMv_RFihrECG3N5vRg

When the JWT configuration is completed, you will need your JWT id to put in the .env file below.

Put these two bits of information will be put in their respective spots in the following file.

Linux

/home/mirc/.env

or

Windows
C:\MIRC\.env

Reboot your new MIRC server.  Everything should start automatically without a need to log in.

RingCentral: Delayed or missing Calls In Queue dialog box.

 If you are not seeing the Calls In Queue window popping when there are calls in queue and you have verified that you are a member of that queue to be an eligible agent, ensure that the time on the PC is correct.  If it is off, you will experience delays in this screen populating.  This delay will be equal to the time drift of the PC.  If the clock is off by 2 minutes, the Calls In Queue window will not populate for 2 minutes.  

RingCentral: Licensing

You can manage your RingCentral licenses in our license management portal.

 Bridge License Management

You will log into the portal using your RingCentral credentials.

Permission to log in is based on your RingCentral role permissions. 
We get all of our “rights” from the user’s role at Ring Central.

At a minimum, your role must have purchasing permission.

Common RingCentral predefined roles would be Billing Admin or Super Admin

If you do not wish to use one of those predefined roles, you will have to create your own role, with the rights listed below.

The user must have one of the following permissions…

Account Administration       AccountAdministration

Device Orders                    DeviceOrdering

Payment Method                EditPaymentMethod

Billing Information              EditServicePlanInfo

Roles                                  EditUserRoles

Payment Method                PaymentMethod

RingCentral: Preparing for selective call queue pickup

 

Bridge Operator Console allows an operator to select a specific call from a call queue.  Sometimes this function is called "cherry picking". 
This will also allow the operator to continue to take calls out of a call queue even though they may already have a queue call on hold.

This function does require that the operator is a member of the Queue Pickup Group for any queue they want to pick from.  This is configured in the RingCentral service portal. 

Here is a link to that configuration step.

Setting up Call Queue Pickup Groups

RingCentral: Repairing Token Process

As a result of recent browser security changes, we needed to institute a new method for the periodic renewal of the security token between the browser and RingCentral.  The new method utilizes a browser pop up.  For this new method to work, you must not block pop ups from the website.
We also recommend logging out of the console at the end of each day.

https://bridge-oc-cloud-app.azurewebsites.net

Also, you should do a force reload of the website to ensure that any previous blocks have not prevented the new code from being downloaded.

Follow the steps below to complete this process.

1. Sign into the Bridge Operator Console for RingCentral.

2. Go into Settings.  Search for "pop-ups".  Follow the links as shown to add/change our website so that pop-ups are allowed.

3. While holding down the Shift Key, press the F5 key.  This should prompt a reload and require you to login once again.  If it does not, the browser did not recognize the command and you will need to do it manually.  This process is pretty similar between Chrome and Edge.
The graphics below will show the steps in each browser.

CHROME

EDGE

RingCentral: Configuring Google App for BOC RingCentral integration

To enable Google integration in the BOC Application, you will need to configure a Google App.

This only needs to be done once per organization.  This is normally done by your Google Administrator.

Sign into your Google Cloud Platform administration page.
https://console.cloud.google.com/

You will need to enable the Admin SDK API and the Google People API.

Admin SDK API

Google People API

API Keys

OAuth 2.0 Client IDs

Authorized JavaScript origins
https://bridge-oc-cloud-app-preview.azurewebsites.net
https://bridge-oc-cloud-app.azurewebsites.net
https://cloud.bridgeoc.com


Authorized redirect URIs
https://bridge-oc-cloud-app-preview.azurewebsites.net/rcconsole.html
https://bridge-oc-cloud-app.azurewebsites.net/rcconsole.html
https://cloud.bridgeoc.com/rcconsole.html




BOC Settings

When the above is completed, you can
gather the Client ID and the API Key and paste them into your console settings.

Once you have entered the Google App Client ID and the Google App API Key you can click Save App Settings. Then you can enable it by moving the slider to the right.
Shortly after moving the slider, you will get a Google authentication prompt.
You must use an email address that has a valid Google account. It does not have to match the RingCentral login used to sign into the application.


This prompt will likely happen a second time as the API is initialized.