Specifications of MVTS II

Session Routing

Elaborate dynamic look-ahead routing based on:

cost (LCR etc.)
route ASR
QoS
average call duration (ACD)
gateway/route load
route capacity
precedence/accessibility of destination GW
number of calling/called party
routing groups
equipment groups
day of week/time of day
ENUM registry lookups

Load Balancing:

Between signaling and media servers in distributed configuration

Interoperability

Carrier-to-carrier and carrier-to-enterprise interoperability:

Support for H.323 and SIP dialects
Two-way SIP/H.323 conversion
Codec support and conversion (G.729, G.729A, G.723.1, G711A-Law, G.711mU-Law, GSM FR, Speex, iLBC)
T.38 fax passthrough

Network Security:

Network Topology Hiding
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

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
100 fields for exhaustive call analysis and preliminary debugging (Call ID, Disconnect Codes, Connect Time, Elapsed Time, QoS, Rate Plan Currency and more)
All relevant call details for complex billing of end-users
CDRs in MIND CTI and MVTS intrinsic formats

RADIUS Accounting for integration with billing systems:

Cisco VSA compliant
Real-time and postpaid billing *
User authorization in billing system based on MVTS data (no authorization in MVTS required)

H.323 Gatekeeper and SIP Registrar Functionality

Zone management
Registration of terminal devices
Dynamic registrations
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

Supported protocols

H.323 v.2 and later (including H.245 v.7, H.225 v.4)
SIP v.2.0 (RFC 2543bis/3261)
RADIUS Accounting

Operating systems

Traffic Switch:

Debian Linux kernel 2.6 32-bit

Traffic Manager (32/64-bit platforms):

Suse Linux Enterprise Server 9
Suse Linux Enterprise Server 10
Red Hat Enterprise AS/ES 3
Red Hat Enterprise AS/ES 4
Red Hat Enterprise AS/ES 5

Database

Oracle 10.2

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)

Fault Tolerance and Redundancy

Remote SNMP monitoring by means of the MVTS Manager or SNMP-counter
Embedded 'watch dog'
Fault-triggered e-mail alerts to system administrator
Failover MVTS server (system redundancy)

Manageability

GUI Web interface
System administration console

Minimal System Requirements

Depend on the system configurations and required capacity

Capacity

Up to 10,000 concurrent calls
Call accretion rate (CPS): 100
New registrations per second: up to 100

Minimal configuration capacity (2 servers):

Up to 1,000 concurrent calls (without codec conversion)

Signaling node capacity:

Up to 150 CPS

Media node capacity (no codec conversion):

up to 1000 concurrent calls

Media node codec conversion capability

“Heavy” codec conversion (G.723 <-> G.729): up to 50 concurrent calls per processor core
“Light” codec conversion (G.711 <-> ANY): up to 100 concurrent calls per processor core

* Add-on billing systems required
** In future releases