MVTS Pro Technical Specifications (Coming soon)
Carrier-to-Carrier/Carrier-to-Enterprise Interoperability
- SIP/H.323 proxy
- SIP/H.323 interworking
- Conversion of media codecs (G.729, G.729A, G.723.1, G711A-Law, G.711mU-Law, GSM FR, Speex, iLBC)
- T.38 fax pass-through
- 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 2543 bis/3261)
- T.38
- SNMP
- RADIUS AAA
- RADIUS routing
Network Security
- NAT/Firewall 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
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
External routing:
- is enabled by RADIUS API which works as a tool of connection to 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
- ÑDRs 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
- Zone management
- RAS-user registration (end-point and other equipment)
- ARQ/LRQ interaction with other networks
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
Configuration and System Management
Configuration and control is performed via user-friendly Web-interface and a GUI.
Web-Interface Functionality
- 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
System Capacity
- Up to 50,000 concurrent calls
- New calls per second (CPS):
- up to 1000 under H.323
- up to 700 under SIP
- New registrations per second: up to 500
- Minimal configuration capacity (all modules are installed on one server and backed up on the second server):
- Up to 1000 concurrent calls (without codec conversion)
- Up to 5000 concurrent calls (in signaling proxy mode)
- Signaling node capacity: up to 150 CPS per processor core
- Media node capacity (without codec conversion): up to 1000 concurrent calls per processor core
- Media node codec conversion capability:
- G.723 <-> G.729 codec conversion: Up to 50 concurrent calls per processor core
- G.711 <-> ANY codec conversion: Up to 100 concurrent call per processor core
MVTS Pro is interoperable with the following gateways and softswitches:
- Cisco
- Quintum
- AudioCodes
- ICG
- Asterisk SS
- SER
- Samsung
- Nextone
- Nortel Succession, BCM
Operating System
- Debian GNU/Linux Etch
Database
- MySQL
