AudioCodes Mediant 4000 SBC, Руководство пользователя

Страница: 641 / 1037

CHAPTER 28 Advanced SBC Features
Mediant 4000 SBC | User's Manual
When the device operates in High-Availability (HA) mode, if a WebSocket connection
has been established and a switchover subsequently occurs, the WebSocket session
is not copied to the redundant device. As Chrome does not renew the WebSocket
connection with the device, WebRTC calls remain open indefinitely; the Chrome side
will stop the call, but the device will keep all of the call's resources open and the other
side will have an active call with no voice. To prevent this, for the IP Profile associated
with the WebRTC clients, configure the 'Broken Connection Mode' parameter to
Disconnect.
Configuring WebRTC
To support WebRTC, you need to perform special configuration settings for the device's SBC leg
interfacing with the WebRTC client (i.e., Web browser), as described in the following procedure.
For the WebRTC deployment environment, you need to install a signed certificate by a Certificate
Authority (CA) on you Web server machine (hosting the WebRTC JavaScript) and on your
AudioCodes SBC device (i.e., WebSocket server).
● Google announced a security policy change that impacts new versions of the
Chrome Web browser. Any Web site that has integrated WebRTC, geolocation
technology, screen-sharing and more, now requires to be served from a secure
(HTTPS) site, including WebRTC-based WebSocket servers (WSS instead of
WS). The configuration described below accommodates for this basic requirement.
● WebRTC JavaScript configuration is beyond the scope of this document.
● The device's WebRTC feature ( WebRTC Gateway ) can also operate with mobile
device users that are registered to the device's WebRTC service, allowing them to
make and receive WebRTC calls between registered users. For this support, you
can use AudioCodes WebRTC client Software Development Kit (SDK) and
Application Program Interface (API) to integrate the WebRTC functionality into the
mobile applications (iOS and Android). For more information, refer to the:
✔
WebRTC iOS Client SDK API Reference Guide
✔
WebRTC Android Client SDK API Reference Guide
● For integrating the device's WebRTC functionality into client Web browsers for
making calls from their Web browsers through the device, you can use AudioCodes
WebRTC client Software Development Kit (SDK) and Application Program
Interface (API). For more information, refer to the
WebRTC Web Browser Client
SDK API Reference Guide .
➢
To configure WebRTC:
1. Configure a TLS Context (certification):
a. Open the TLS Contexts table (see Configuring TLS Certificate Contexts ).
b. Add a new TLS Context (e.g., "WebRTC") or edit an existing one and configure the DTLS
version (TLSContexts_DTLSVersion).
c. Create a certificate signing request (CSR) to request a digitally signed certificate from a
Certification Authority (CA).
d. Send the CSR to the CA for signing.
e. When you have received the signed certificate, install it on the device as the "Device
Certificate" and install the CA's root certificate into the device's trusted root store
("Trusted Certificates").
For more information on CSR, see Assigning CSR-based Certificates to TLS Contexts .
- 608 -