Specifications of MVTS Pro

Supported codecs

• H.261, H.263, H.264 video pass-through
• Conversion of media codecs (G.729 (plain, A,B, AB), G.723.1, G.711, GSM FR, Speex, iLBC)
• Protocol normalization to ensure seamless interoperability

Supported Protocols

• H.323 v.2 and later (including H.245 v.7, H.225 v.4)
• SIP v.2.0 (RFC 3261)
• ETSI/ITU ISUP (SIGTRAN)*, MGCP support on the core level
• SIP/H.323/ ETSI/ITU ISUP (SIGTRAN)* conversion
• SIP-T/I
• T.38
• SNMP
• RADIUS AAA
• RADIUS-based routing
• ENUM

*national dialects are implemented on demand

Configuration and System Management

Configuration and control is performed via user-friendly Web-interface and a GUI.

• Real-time configuration
• Multiple users with granular access rights
• Active calls monitoring (originating/terminating Gateway, duration, used codecs etc.)
• Automated call blocking based on account balance or other parameters
• Active gatekeepers/registrars/endpoints monitoring
• Traffic Switch runtime statistics (over 100 counters)
• CDRs in plain text format convenient for analysis and preliminary debugging
• CDR filtering by any call parameter
• Export and import of configuration files

Traffic Routing

Own routing mechanism allows routing policies based on:

• The number of the calling/called party
• The route's answer seizure ratio (ASR)
• Gateway/route traffic load
• Caller ID group (one gateway can belong to several groups)
• Day of week/time of day

Externally aided routing:

• is enabled by a RADIUS API, which functions as a means of connection with third-party routing systems
• is possible by any criteria relevant for an external routing system

Statistics and Operation Analysis

• Real-time monitoring of answer seizure ratio (ASR), quality of service (QoS), average call delay (ACD), disconnect codes, etc.
• Call statistics monitoring by route/gateway
• CDR-based call analysis
• CDRs in plain text format convenient for analysis and preliminary debugging
• CDR filtering by any call parameter
• Preliminary debug data collection
• Export of CDRs in CSV format

Accounting

Call Detail Records (CDRs):

• Single point for CDR collection
• Exhaustive number of fields for detailed call analysis and preliminary debugging (Call ID, Disconnect Codes, Connect Time, Elapsed Time, etc.)
• All relevant call details for flexible billing of end-users RADIUS API that allows integration with third-party billing systems
• Cisco VSA compliant
• User authorization in billing systems based on MVTS Pro data

H.323 Gatekeeper Functionality

• RAS registration of endpoint and other equipment
• Internetworking as a gatekeeper

Number Transformation

• Regexp-based number modification patterns and rules
• Calling/called party number transformation as required by partner carriers
• Calling party number disguise
• Differentiated number transformation for the purposes of billing and routing

Total capacity

New calls per second (CPS):

• unlimited (up to 1,000 CPS per 1 traffic entry point)

Concurrent calls:

• up to 150, 000 per cluster

BHCA:

• up to 10,000,000

Increase in capacity

System capacity scales up almost linearly with an increase of processor cores’ number in cluster as well as respective RAM growth.

Operating systems:

• Debian GNU/Linux Lenny

Database:

• MySQL

Network Security

• NAT traversal
• Network topology hiding
• Call authorization by IP address or user name and password, based on:
  • data from internal MVTS Pro configurations
  • data from external billing systems