MVTS II Architecture

MVTS II consists of two functional layers: the switching layer, comprised of one or more Traffic Switches (TS), and the management layer referred to as Traffic Manager (TM).

Traffic Switch (TS)
Traffic Switch (TS) handles VoIP calls according to the logic provided by Traffic Manager, generates call session data, and acts as an SBC, ensuring protocol translation and normalization, network topology hiding, DoS attack prevention, NAT traversal, and codec conversion.

TS incorporates the following main types of functional modules:

• Load Balancers / H.323 Gatekeepers / SIP Registrars
• Signaling Nodes – signaling processing and SIP<->H.323 conversion
• Media Nodes – RTP traffic proxying and codec conversion

MVTS II supports license-dependent dynamic load that ensures automatic distribution of traffic between servers based on their current workload.
Distributed architecture of the MVTS II switching layer allows for:

• excellent scalability and high fault tolerance
• building geographically distributed networks with a single point management and data entry
• flexibility and ease of adding additional servers into a cluster

In case of a hardware fault in any of the system’s components, its functions are automatically taken over by other servers in the cluster, assuring business-critical system dependability.

Traffic Manager (TM)
Traffic Manager contains the system’s intellect and repository of data. It’s an Oracle-based routing and billing core of the system and the central point of storage for all configuration, statistical, CDR, and billing data. Traffic Manager is also responsible for authentications and call admission control, call routing algorithms, statistical analysis, notifications and alerting, and Web GUI management.