Architecture

Altitude VoIP network requirements for using Altitude vBox WebRTC All-in-One.

Security protocols

The secure default protocols to use on authentication to Altitude vBox WebRTC All-in-One are:

• TLS 1.2
• TLS 1.3

Versions and compatibility

The following table describes the compatibility between Altitude vBox WebRTC All-in-One and the Altitude uCI Server:

The following table describes the compatibility between the Altitude vBox WebRTC VHD image and the Altitude uCI Server:

How to install Altitude vBox WebRTC in virtualized environments

Altitude vBox WebRTC is available using the following:

• An OVA image.
• An ISO file.

The following table displays the recommended installation of Altitude vBox WebRTC, depending on the environment:

Altitude vBox WebRTC trunk architecture

VoIP network requirements with Altitude vBox WebRTC All-in-One are the following:

• Fully switched
• Bandwidth of 100Mbps
• Service quality (recommended):
  • Layer 2 (CoS or 802.1p)
  • For remote links between agents workstations and Altitude vBox WebRTC All-in-One, use Layer 3 (QoS) with end-to-end technology .

The Altitude vBox WebRTC All-in-One connects to the VoIP network using UDP SIP trunks to:

• Altitude vBox 5.1
• Altitude vBox WebRTC All-in-One
• Altitude Communication Server (used as Call Classifier)
• Asterisk
• SIP servers and SIP providers with a successful and documented interoperability test with Altitude vBox WebRTC All-in-One.

You can use all types of trunks (SIP and VoIP calls) on the same Altitude vBox WebRTC All-in-One.

WebRTC integration

In order to integrate WebRTC with Altitude vBox WebRTC All-in-One, please see WebRTC integration.

Operational parameters

The network must have the following operational parameters:

• End-to-end one-way latency up to 150ms.

  Note Agent phones may consume part of the latency through jitter buffers.

• Packet loss up to 1%.
• The value of jitter must match the phone configuration. For example, threshold of 10 ms.
• Enough bandwidth to support the target number of agents with the selected codec.

Recording formats

Altitude vBox WebRTC can record calls in the following formats:

• GSM
• WAV

WAV files require more disk space, while GSM files use less bandwidth when transferred to an Altitude Recorder Storage Server. Altitude recommends the GSM format.

You can also configure Altitude vBox WebRTC to record both legs from a call, only the agent leg, or both legs in stereo.

Remote connections

Altitude vBox WebRTC All-in-One servers should be in the same LAN, and can have remote connections to the following components:

• Telephony gateway.
• Altitude Recorder Storage Server.
• SIP provider.
• Altitude Communication Server.

Connection to agent extensions

Connect agent phones as follows:

• Agent phones must have access to the IP address of Altitude vBox WebRTC All-in-One. Altitude vBox WebRTC All-in-One must have access to the agent phones and, if phones are behind NAT (Network Address Translation), you must configure a specific firewall so that vBox receives signaling from the agent phones with reachable addresses and not private IP addresses.
• Altitude vBox WebRTC can be used with extensions in the public Internet, using one of the following configurations:
  • One NIC with an internal IP, mapped to an external IP address through NAT
  • Two NICs, one with an internal IP, and the other with an external IP address.

Guidelines

• To reduce WAN bandwidth requirements, deploy the telephony gateway and Altitude vBox WebRTC All-in-One in the same LAN and connect the telephony gateway to the Altitude uCI Server using the WAN.