In some circumstances, particularly for troubleshooting, it may be useful to explicitly define which webRTC server or region your Sharpen Q Phone or Connect phone is connecting to. This article describes how to identify which server you’re currently connected to, as well as how to temporarily connect to a different server or region.
Please note that utilizing this method avoids load balancing which occurs in the webRTC environment. We recommend only using this method temporarily during troubleshooting efforts.
Identify your current webRTC server
Login to Sharpen Q or Sharpen Connect
Right-click in an empty area within the browser window and choose ‘Inspect’
Choose the ‘console’ tab and type ‘server’ into the window as shown below
The server fully qualified domain name is listed after hitting enter on the keyboard
If using Sharpen Connect, the steps to identify the server are the same. However, it will likely open Chrome dev tools in a separate window. If you are unable to locate dev tools, make sure to check additional monitors or workspaces
Connecting to a different server or region
It is important to consider that establishing a new connection requires a new login. Before following the steps below, please logout of your Sharpen session, whether it be Sharpen Q or Connect.
Sharpen Q
Simply utilize the following URL for login with the appropriate server or region.
iz0 - This is your environment if you login to app.sharpencx.com
iz1 - This is your environment if you login to app.iz1.sharpen.cx
iz0 isolation zone
Region
https://app.sharpencx.com/fathomQ/dashboard/?region=XXX
Specific server
https://app.sharpencx.com/fathomQ/dashboard/?region=XXX-##
iz1 isolation zone
Region
https://app.iz1.sharpen.cx/fathomQ/dashboard/?region=XXX
Specific server
https://app.iz1.sharpen.cx/fathomQ/dashboard/?region=XXX-##
For example, if we wanted to connect to the EU region, we could do so by entering… https://app.sharpencx.com/fathomQ/dashboard/?region=EU2
If we wanted to connect to a specific EU server (eu2-webrtc-01), we could do so by entering… https://app.sharpencx.com/fathomQ/dashboard/?region=EU2-01
Connect
Similar to Sharpen Q, simply utilize the URL in the following format
iz0 isolation zone
Region
https://connect.sharpencx.com/?region=XXX
Specific server
https://connect.sharpencx.com/?region=XXX-##
iz1 isolation zone
Region
https://connect.iz1.sharpen.cx/?region=XXX
Specific server
https://connect.iz1.sharpen.cx/?region=XXX-##
Validation
To validate the change, simply execute the steps above in the 'Identify your current webRTC server' section.
What Does Prism WebRTC Notation Mean?
There are 2 entries per WebRTC instance in Prism because there are two separate ways to access a WebRTC server.
There’s a “service” account that is used for pointing/testing directly to the WebRTC instance (intended for testing, Care team troubleshooting, or internal QA work before releasing a new WebRTC into the wild).
There’s also the normal account usage, which is when traffic can get passed through to the WebRTC server via the load balancer.
Example usage:
