WebRTC integration

Integration of WebRTC with Altitude vBox, HTTPS, and a proxy.

The following content is applicable to the following versions of Altitude vBox:

• Altitude vBox WebRTC (Altitude vBox 6)
• Altitude vBox 7.

The integration of WebRTC with Altitude vBox can be done using one of the following architectures:

• Internal network: All components of the architecture are in the same network. Agents access uAgent through the internal network. The internal network architecture can have additional components and configurations, depending on whether the SIP provider has an IP address in the same network as the remaining components, or an IP address external to the network.
• External network: All components of the architecture are in the same network. Agents can access uAgent either through the internal network or an external network. The SIP provider is located at an external network, with a public IP address.

Certificates

WebRTC only works with HTTPS. You should have certificates from a recognized certification authority, which ensures the platform works out of the box without the need to configure exceptions or import certificates in the browsers.

Please consider the following when creating or using certificates:

• The certificate should have a Subject Alternative Names (SAN) field. Google Chrome issues a warning if the certificate does not have a SAN field.
• The Common Name (CN) and SAN fields of the certificate should be a fully qualified domain name (FQDN), and must match the public URL that agents will use to access uAgent Web. For example, uagent.mycompany.com.

Use one of the following options when considering certificates:

• Have one multi-domain certificate (SAN certificate), issued for your FQDN. For example, a certificate which contains the FQDN sbc.mycompany.com and uagent.fqdn.com. You can use the same certificate for the SBC and uAgent servers, and it is a more secure practice.
• Have one wildcard certificate issued for all URLs in your fully qualified domain name (FQDN). For example, a certificate for *.mycompany.com. With a wildcard certificate, you can use the same certificate for the SBC and uAgent servers, but it is a less secure practice.
• Have different certificates for the SBC and uAgent servers.

Troubleshooting

• If you cannot set a WebRTC extension, ensure the SBC address in the uAgent Web configuration file matches the domain configured in the WebRTC NAP of the WebRTC SBC, and the TLS certificate configured in the global VoIP settings is valid.
• If calls drop after 32 seconds when NAP is configured with an FQDN, enable Ignore field "Contact" from headers, using "To" instead in the global VoIP settings.
• If the PSTN SBC fails to identify the origin NAP of INVITEs received from a client Altitude vBox when using an Altitude vBox WebRTC or Altitude vBox 7, enable Use origin by IP packet address in the NAP for Altitude vBox.
• If audio is lost one way after a few seconds, and the call is dropped after 5 minutes, in Altitude vBox, set session timers to refuse in the WebRTC extensions.
• If the call is immediately dropped, check if the codecs match in Altitude vBox extensions and in the SBC WebRTC configuration.