Specifications of MVTS
Session Routing
Internal routing based on- Route ASR
- Gateway/route load
- Precedence/accessibility of destination GW
- Number of calling/called party
- Caller group ID
- Day of week/time of day
- RADIUS API for interaction with add-on routing systems
- LCR (Least Cost Routing) by add-on engines
- Between the gateways of a dial peer (Round-Robin, Lowest or Highest Utilization)
- Between physical Internet links (bandwidth management)
- Between signaling servers in distributed configuration (for better fault-tolerance)
Interoperability
Carrier-to-Carrier/Carrier-to-Enterprise- Support for H.323 and SIP dialects
- SIP/H.323 interworking
- Two-way SIP/H.323 conversion
- SIP stateful proxy
- Conversion of media codecs (G.729, G.729A, G.723.1, G711A-Law, G.711mU-Law, Speex, ILBC, GSM FR)
- T.38 fax pass-through
- Direct IP connectivity with SIP and/or H.323-based IP PBX
Network Security
- NAT/Firewall traversal
- Network Topology Hiding
- DoS (Denial of Service) attack prevention
- Call Admission Control (max calls on ingress, max calls on egress, total max calls per direction/route)
- Call authorization by IP address or user name and password, based on
- Data from internal MVTS configurations
- Data from external billing system
Call Statistics and Analysis
- Real-time monitoring of ASR, QoS, ACD, disconnect codes
- Call statistics monitoring by destination/GW
- CDR-based call analysis
- CDR in plain text format convenient for analysis and preliminary debugging
- CDR filtering by any call parameter
Billing and Accounting
CDR (Call Detail Records)- Single point for CDR collection
- 39 fields for exhaustive call analysis and preliminary debugging (Call ID, Disconnect Codes, Connect Time, Elapsed Time, and more)
- All relevant call details for complex billing of end-users
- CDRs in MIND CTI and MVTS intrinsic formats
- Cisco VSA compliant
- Real-time and postpaid billing*
- User authorization in billing system based on MVTS data (no authorization in MVTS required)
- Automated call blocking based on account balance
H.323 Gatekeeper Functionality
- Zone management
- RAS registration of terminal and other devices
- IP-to-IP GW (CAC based on originator IP address, no RAS authorization required)
- Capability to interoperate with upstream gatekeepers
Number Translation/Normalization
- Regexp-based number translation patterns and rules
- Number translation applied at ingress, egress or within MVTS
- Source/destination number translation as required by different carriers
- Source number disguise
- Differentiated translation for billing reports and routing
Supported Protocols
- H.323 v.2 (including H.245 v.7, H.225 v.4)
- SIP v.2.0 (RFC 2543bis)
- T.38, T.120
- SNMP v.1 (statistics and trap)
- MD5, CHAP
- RADIUS authentication
- RADIUS accounting (Attribute 44 and VSA)
- RADIUS routing
Operating Systems
- Linux RedHat 9.0
- Linux RedHat Enterprise 3.0, 4.0
- Linux RedHat Advanced Server 3
- Linux Fedora Core 3, 4
- Free BSD 5.0+ (trial version only)
System Logs and Journals
- Call handling trace logs with selectable detail level options
- Billing and debug logs
- Call data extraction based on the call ID (log extractor script)
- Call log viewing by means of the MVTS Manager
- Automated log management: archiving, file size and rotation control
Fault Tolerance and Redundancy
- Remote SNMP monitoring by means of the MVTS Manager or SNMP-counter
- Embedded 'watch dog' timer
- Fault-triggered e-mail alerts to system administrator
- Failover MVTS server (system redundancy)
- Backup RADIUS server configuration
Manageability
- MVTS Manager (Windows-based GUI for remote monitoring and control)
- Configuration files in plain text format
- System administration console
- Web Monitor (web-based utility for remote system monitoring)
Minimal System Requirements
For signaling proxy operation only- 30 calls — Pentium III 933GHz/256Mb RAM/20Gb HDD/100Mb Ethernet
- 60 calls — Pentium III 933GHz/512Mb RAM/20Gb HDD/100Mb Ethernet
- 120 calls — Pentium III 1.13GHz/512Mb RAM/20Gb HDD/100Mb Ethernet
- 300 calls — Pentium III 1.2GHz/512Mb RAM/20Gb HDD/100Mb Ethernet
- 500 calls — Pentium IV 1.4GHz/1024Mb RAM/40Gb HDD/1Gb Ethernet
- 30 calls — Pentium III 1.13GHz/256Mb RAM/20Gb HDD/100Mb Ethernet
- 60 calls — Pentium III 1.2GHz/512Mb RAM/20Gb HDD/100Mb Ethernet
- 120 calls — Pentium IV 1.4/512Mb RAM/20Gb HDD/100Mb Ethernet
- 300 calls — Pentium IV 1.8/1024Mb RAM/40Gb HDD/100Mb Ethernet
- 500 calls — Xeon Pentium IV 2.4/2048Mb RAM/40Gb HDD/1Gb Ethernet
Scalability
- Scalable from 30 up to 500 concurrent calls (H.323 sessions in full proxy mode)
- Upgradable within less than 5 minutes
- Remote upgrades possible
- Protection against data loss during upgrade
Compatibility List
SIP and H.323 gatekeepers and gateways- AudioCodes
- Cisco Systems
- Cirpack
- Clarent
- Grandstream
- Lucent
- Nuera
- Quintum
- Samsung
- Sonus
- Telica
- VocalTec
- Absolut
- Advanced VoIP Billing System
- CBOSS
- EyeBill
- IPSoft Billing
- Livingstone Radius
- MIND CTI
- Porta Billing,
- T-Soft Billing
- Yard
- Alcatel
- Avaya
- Broadsoft
- Cisco Systems
- Clarent
- NetCentrex
- Nortel Networks
- Nuera
- Siemens
- Sonus
- Sylantro
- VocalTec
* Add-on billing systems required
