Web Phone

Setup Integrations Web Phone

The ConnexCS Web Phone runs directly from a browser without the need to install anything, allowing customers to make calls via the internet using a softphone. If the user wishes to install the application, additional functionality can become available (ex: push notification capabilities while the app is closed). With application cross-platform functionality (including Windows, Mac, Android, iOS, etc) this makes it ideal in call center and other similar deployments.

iOS limitations

iOS limits the ability to perform push notifications.

Technical Details

Application

ConnexCS Web Phone is a WebRTC application using PWA. WebRTC (Real-Time Communications) is a browser protocol which runs on top of an HTTPS connection. ConnexCS Web Phone uses WebRTC (HTTPS port 443) for SIP Signaling and WebSockets (random UDP ports) for the Media.

BitDefender and WebSockets

BitDefender blocks WebSockets unless the phone. and webrtc. domains have been whitelisted.

A PWA (Progressive Web Application) is an application written inside the web browser, and it uses a modern API.

State-level firewalls

WebRTC is effective for bypassing state-level firewalls by:

1. Running Signaling over a widely unblocked port (443).
2. Sending all Data (Signaling and Media) over an encrypted connection.

Security and Encryption

ConnexCS Web Phone encrypts all information (Signaling & Media) between the browser and the ConnexCS platform. This is accomplished by leveraging TLS (Transport Layer Security) protocol support on the underlying browsers. Currently, all modern browsers support TLS 1.0, 1.1, 1.2 & 1.3.

MITM (Man-in-the-Middle) attacks actively intercept traffic between endpoints, while still operating within a TLS framework. This type of attack is counteracted with PKI (Public Key Infrastructure), a native HTTPS feature. PKI ensures end-point integrity, so you can be confident the endpoint you connect with is the one you expect without any intermediaries.

TLS 1.3 Support

ConnexCS Currently does not support TLS 1.3. This functionality is scheduled to be completed by Q3 2020.

Debugging SIP Messages

If you need to debug Web Phone and see the SIP messages, you can enter *#0*# into the dial pad, this will switch on debugging mode in the browser console.

Navigation

Navigate using the following sections in the footer menu at the bottom of Web Phone (see Menu tab under Config Options below to change how these are displayed):

• Agent: Preview dialer
• History: Previously dialed numbers and extensions
• Dialpad: Dialpad for making and answering calls
• Contacts: This is the same Contacts databased configured under Class5 Phonebook
• Settings: View the Display Name, SIP information, and WS URL

Enable Web Phone

Setup Domains

ConnexCS Web Phone needs 2 domains to function correctly:

1. Web Server (Domain A) - This is the location where the phone is hosted, and the URL which is provided to your customers. Create a CNAME on your domain, such as webphone.yourdomain.com, and point it to our web server at portal.connexcs.com (responsible for web services, and yes, this is the same as the customer portal).
2. SIP Switch (Domain B) - This is the SIP signaling domain (WebRTC) and is attached to your server. Navigate to Setup Settings DNS . Enter the domain (ex: test1), then check the box for the A record for the IP of the server you want to use.

It is recommended to setup a DNS record within ConnexCS, then point a CNAME on your domain to the ConnexCS setup domain.

Create Certificates

After the domains are configured, verify the certificates are under **Setup Information Certificates:

• If the domain is not listed, click on Add Certificate and provide your domain name.
• If the certificates are listed but they don't have an issue or expiry date, click on "Refresh Certificates". This may take up to 10 minutes to complete.

Add WebRTC to server

To setup WebRTC on a server:

1. Ensure Domain (B) (signaling domain from above) points ONLY to the server where you enable WebRTC.
2. Navigate to Setup Settings Servers select the server, then Edit.
   • Update the FQDN to the server
   • Ensure that both TLS and WebRTC are enabled
   • Run Install Server if any settings were changed

AnyEdge and WebRTC

If you are using AnyEdge, you can enable WebRTC automatically by adding a domain name to your AnyEdge Domain.

Setup Web Phone Domain

Once domains, certificates, and server settings are updated, we can add the Web Phone domain.

1. Go to Setup Integrations Web Phone
2. For Domain, enter Domain (A)
3. Set WebRTC Host as Domain (B)
4. Click Save

Your Web Phone should now be available.

Configure Web Phone

Click each tab to view configuration details.

BasicMenuAdvanced

• Domain - The URL where the Web Phone is accessed (Domain A from the initial Web Phone setup).
• Brand Name - This is what will display in the Web Phone; your Account name will not be displayed.
• WebRTC Host - The primary end point (server address) that you will connect to (Domain B from the initial Setup Domains above). This is always a domain name and can be pointed directly to a server or to AnyEdge.
• Template Customer - A pre-configured customer on your account which is used to hold the default values for independently created customers. Available values for this template customer are:
  • Customer [Fields in the customer itself, such as debit limit]
  • Routes
  • Payments
  • Alerts
  • Packages
  • Contracts
• Register Success HTML - Customize a message to display to customers once they have completed their signup process.

 

Template Customer Example

You want to give all your customers $5.00 credit. Create an account under Management Customer. Under Payments for that account, add $5.00. When a new customer creates an account from the Customer Portal, they will see a payment created for $5.00 at the same the time account was created.

Configure the Web Phone footer menu:

• Title - The label used for this page.
• Icon - The Icon displayed in this position. (Web Phone uses Material Design. If you wish to change an icon, you can find a list here.
• Position - Determine Icon position, starting with 1 on the far left. Select Disabled if you don't wish to show this item.
• Template - A Custom page can be used to display custom static & dynamic content. These are pre-built under Setup Config Template.

 

Frameless iframe

We have implemented an edge case. If you wish for the custom page to be an iframe, you can use the following code to ensure that it fills up all the available space (replace www.connexcs.com with the page you wish to display):

<!-- NO-CONTAINER -->

<iframe src="https://www.connexcs.com" style="border: 0px; width: 100%;height: 100%"></iframe>

• Flags- Select display options for WebPhone
  • Hide UUID: UUID is a unique deploy & version identifier, this is what you should ask your end user for if you need to report a problem to us. It is displayed in the side menu.
  • Menu Right: Change the normally left menu into a right menu.
  • Display Balance: Show the balance of the account.
  • Edit Settings: As standard settings are non-editable, if you wish to allow a user to change settings, you can change this.
  • Register: Allow registration of new accounts, or only existing SIP Username / Passwords can login.
  • Username as Title: Change the title of the page to the username logged in.
  • Accept Payment: Accept payments, similar to on the customer portal.
  • Auto Answer: Automatically answer an incoming call.
• Restrict Customer Login- Select existing Companies from the dropdown to allow them access to WebPhone. If no companies are listed, then all will have access.

 

Web Phone SDK

The Web Phone SDK (Software Developer Kit) allows developers to integrate WebPhone into your own custom projects. This is available as part of the ConnexCS deployment at no extra charge. The Web Phone SDK Connector provides the developer documentation needed to place a call.

You will need to provide the full URL (ex: http://domain.connexcs.com) and credentials to access Web Phone from within the connector.