Architecture

Altitude VoIP network requirements for using Altitude vBox 7.

Security protocols

The secure default protocols to use for authentication to Altitude vBox 7 are:

  • TLS 1.2
  • TLS 1.3

Versions and compatibility

The following table describes the compatibility between Altitude vBox 7 and the Altitude uCI Server:

Altitude uCI Server update

Altitude vBox 7 version

Update notes

8.6.2100

8.6.2100

First Altitude vBox 7.

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

Altitude uCI Server update

Altitude vBox 7 version

Update notes

8.6.2100

8.6.2100

First Altitude vBox 7.

How to install Altitude vBox 7 in virtualized environments

Altitude vBox 7 is available using the following:

  • A VHD image.
  • An ISO file.

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

Environment

VHD image

ISO file

Microsoft Azure

-

Hyper-V

-

VMware

-

Attention

Altitude does not provide an OVA file for installation in VMware. Use the ISO file instead.

Trunks and network requirements

VoIP network requirements with Altitude vBox 7 are the following:

  • Fully switched
  • Enough bandwidth to support the target number of simultaneous calls.
  • Service quality (recommended):
    • Layer 2 (CoS or 802.1p)
    • For remote links between agents workstations and Altitude vBox 7, use Layer 3 (QoS) with end-to-end technology .

The Altitude vBox 7 connects to the VoIP network using UDP SIP trunks to:

  • Altitude vBox
  • Altitude Communication Server (used as Call Classifier)
  • Asterisk
  • SIP servers and SIP providers with a successful and documented interoperability test with Altitude vBox 7.

You can use all types of trunks (SIP and VoIP calls) on the same Altitude vBox 7.

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, a threshold of 10 ms.
  • Enough bandwidth to support the target number of agents with the selected codec.

Recording formats

Altitude vBox 7 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.

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

If you are using Altitude Recorder 2, the Altitude Recorder 2 reencodes calls to the Opus codec.

Important

  • Stereo mode is only supported if the encoding format is WAV, since the GSM format is not multi-channel.
  • Recordings in stereo are twice the size, and decreases performance.

Remote connections

Altitude vBox 7 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 7. Altitude vBox 7 must have access to the agent phones and, if phones are behind NAT, 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 7 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 7 in the same LAN and connect the telephony gateway to the Altitude uCI Server using the WAN.