MX Platform
Architecture Overview
Table of Contents
MPATHIX MX PLATFORM: OVERVIEW...1
Open Architecture...1
Transitioning to VoIP?...1
MX PLATFORM MULTI-TIERED ARCHITECTURE...1
Key Architectural Interfaces...2
Signalling Interfaces...2
Transport...2
Notification...2
Network Interoperability...3
Unified Messaging...3
Provisioning, Administration, and Maintenance...3
Billing, OM, and Data Reporting...4
System Monitoring...4
NETWORK ARCHITECTURE...4
Centralized Configurations...4
Distributed Configurations...6
Hybrid Configurations...7
Configurations in Hybrid TDM-IP Networks...8
Mpathix MX Platform: Overview
Based on open architecture, the Mpathix MX platform uses industry-proven components and exceeds carrier standards for high availability and scalability. Supporting common industry standards and protocols, including SIP, SS7, SMPP, SNMP, XML, VPIM and TCP-IP, Mpathix ensures ultimate compatibility and ease of integration into operator networks.
The MX platform is especially compelling to service providers planning to upgrade to an IP network. By simultaneously supporting SS7 and SIP protocols on the same server, Mpathix ensures a smooth and seamless transition to IP messaging.
The platform supports voicemail, faxmail, auto attendant, unified messaging and a host of next generation features. The integration of 3rd party technologies enables the rapid introduction of new services and ensures that carrier needs are met today and into the future.
Open Architecture
A truly open system, the Mpathix MX platform combines the power of the best telecom equipment providers with our superior software to provide a complete voice messaging solution. Continued use of best-of-breed components ensures that operators will not be tied to obsolete equipment.
With the integration of the latest 3rd party technologies, service providers can easily offer innovative features. Mpathix provides basic and enhanced features on a single, expandable platform.
Since the beginning, Mpathix has enabled operators to improve the payback period and offer voicemail to all subscribers. The use of industry-proven components and 3rd party technologies – readily available and widely accepted – translate into lower costs for Mpathix, and subsequently, a lower price to service providers. What’s more, common equipment and familiar interfaces lead to less training required and ease of use for carriers since the operations staff can quickly come up to speed with the MX platform.
Transitioning to VoIP?
By supporting both TDM and IP technologies, Mpathix assists service providers in transitioning between them. The platform's simultaneous support of SS7 and SIP protocols ensures that carriers can move towards an IP network smoothly and seamlessly, without compromising on reliability.
With the transition from PSTN to IP, hybrid networks will be a reality for years to come. With Mpathix, service providers enjoy a single, integrated solution for all of their network needs. The MX platform interoperates with industry standard TDM switches, media gateways, and softswitches. The Mpathix design ensures interoperability with existing infrastructure, and supports the full range of network access possibilities based on landline, wireless, and other access technologies.
MX Platform Multi-Tiered Architecture
A smaller footprint than competitive systems allows carriers to make the most of central office real-estate. A fully loaded system fits within two telecom racks – with room to spare.
Key Architectural Interfaces
Signalling Interfaces
SS7 (Connected via A-Links to STP or F-Links to switch) MF Signaling
Session Initiation Protocol (SIP) over IP
Transport
T1 E1
RTP over IP
Notification
TCAP over SS7 Pager over T1/E1
IS-41 Live Outcall Notification over T1/E1
SMDI over RS-232 Email Notification using SMTP or POP3
SMS using SMPP over IP Instant Messaging
SIP SUBSCRIBE/NOTIFY
Network Interoperability
IP to network multiple Mpathix systems VPIM to interface with legacy voicemail systems
POP3 to collect messages stored on other messaging platforms
Unified Messaging
Web browser using HTML and XML
Email client access to messages using SMTP or POP3
Provisioning, Administration, and Maintenance
Command line interface (CLI) via telnet/shell account
Incorporation into existing centralized provisioning system (CLI or XML) MX System Administration Web Interface (see Figure 2)
Billing, OM, and Data Reporting
Billing: System creates Call Detail Records (CDR) for all call and message events OM Data is collected for the following event types:
− Call Activity − MWI Activity − Messaging Activity − Mailbox Activity − Provisioning Activity − IVR activity
− Hardware Resources (System) Reports − Subscriber Reports
System Monitoring
Mpathix provides two systems to help with management of the MX platform:
(1) SNMP System – provides access to 3rd party vendor SNMP MIBs, such as the Solaris SNMP Agent and NMS SNMP Agents
(2) Alarming System – notifies network managers with SNMP traps when events occur in the Mpathix MX software
Network Architecture
The MX platform also provides the ultimate in affordability and network flexibility, economically supporting both centralized and distributed networks. In Figures 3 to 8, several possible configurations are shown, although the system is flexible enough to work in any imaginable configuration. Mpathix will work with you to choose the configuration that best fits your network.
Centralized Configurations
Distributed Configurations
Hybrid Configurations
Configurations in Hybrid TDM-IP Networks
Scalability
Mpathix gives service providers the ability to easily add more capacity when they need it. The Mpathix MX platform can scale up to 1,440 ports (IP and/or TDM) per node and 15,000 hours of fully mirrored message storage by simply adding servers, hard disks and telecom equipment as needed. For large networks, multiple nodes can be linked seamlessly and if capacity grows beyond the initial configuration purchased, Mpathix also provides an expansion path.
Why pay for more capacity than is needed? Unlike some vendors that force carriers to pay upfront for ports that may not be required for years, the MX platform lets operators scale as needed. This gives service providers full control over growth and ensures capital expenses are not tied up for capacity that will not provide a return on investment.
Reliability
With Mpathix, multi-level redundancy is a design fundamental: NEBS™-compliant servers
Component level redundancy: power, CPUs, hard disks, database, SS7 links, T1/E1, VoIP cards Architecture level redundancy: software, media servers, application servers, storage array
Component Reliability Considerations
Disk Storage • Fully Mirrored
• Hot Swappable
Power • Redundant Power Supplies
• Hot Swappable
CPUs • N+1 Redundacy
System Connectivity • Redundant SS7 Connections
The Mpathix MX CX2400 and CX4800 configurations are designed for carriers who require high reliability. The fully redundant architecture includes all of the featured reliability mentioned above, and also includes full redundancy in the system database. These configurations enable upgrades without downtime plus full redundancy and operation protection in the unlikely case of a full server failure. In such an unlikely event, the redundant server handles all call processing.
To ensure the highest availability, Mpathix continues to use best-of-breed components such as Sun Microsystems™ NEBS™-compliant servers. Sun has consistently demonstrated commitment to delivering server technology that is reliable and scalable and its servers are widely deployed by respected carriers around the world.
At Mpathix, component and architectural reliability are an essential part of the platform’s design. Operator networks are complex and each element must adhere to stringent standards to ensure that the overall network meets end-user expectations. The Mpathix MX platform is built for the demanding Central Office environment.
Hardware and Software Components
The use of industry-proven components and 3rd party technologies – readily available and widely accepted – translate into lower costs for Mpathix, and subsequently, a lower price to service providers. What’s more, common equipment and familiar interfaces lead to less training required and ease of use for carriers since the operations staff can quickly come up to speed with the Mpathix MX platform. The recommended hardware and software is shown below.
Component Vendor Product Website
Feature Server Sun Microsystems Netra 440
www.sun.com
Telecom Server Sun Microsystems Netra 440
www.sun.com
UM Server Sun Microsystems Sunfire V240
www.sun.com
Storage Array Sun Microsystems StorEdge 3310
www.sun.com
T1/E1 Cards NMS Communications CG6000 Quad Cards
www.nmscommunications.com
VoIP Cards NMS Communications CG6000
www.nmscommunications.com
SS7 Cards and Stack SS8 SS8 PCI 370 board