21/1551-ASP 113 01 DESCRIPTION 28 01 2014 N2 MX-ONE System Description Catarina Tero Leif tsilvennoinen lisaksson Isaksson Silvennoinen Sten DESCRIPTION
MX-ONE SYSTEM DESCRIPTION Copyright © Copyright Aastra Technologies Limited, 2014. All rights reserved. Disclaimer No part of this document may be reproduced in any form without the written permission of the copyright owner. The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Aastra shall have no liability for any error or damage of any kind resulting from the use of this document.
INTRODUCTION Aastra's BluStar ecosystem provides businesses with a comprehensive, end-to-end UCC solution with a versatile user interface that is used across devices. BluStar offers a natural collaboration experience and fully embraces trends such as rich presence information, IM multi party and personal video communication as well as increased use of smart phones and tablets in the workplace. BluStar helps users work together more effectively, e.g.
MX-ONE SYSTEM DESCRIPTION 2 System Overview This chapter gives a high-level description of the MX-ONE solution. 2.1 General The MX-ONE solution consists of a set of integrated modules, forming a complete communication solution for an enterprise. Figure 1: MX-ONE modules MX-ONE comprises: • • • 4 MX-ONE Telephony System, the IP- and server-based foundation and major building block. For SIP-only deployment, the required media gateway functionality can be provided by software, i.e.
SYSTEM OVERVIEW • • • • 2.2 Contact Management (CMG) is an advanced contact management system for telephony and provides applications for attendants and end-users. OneBox provides features for voice mail and fax mail, including Unified Messaging. Aastra Solidus eCare, a suite of applications and services for server-based contact centers. BluStar Ecosystem, providing multi-media services for end users.
MX-ONE SYSTEM DESCRIPTION DTS, and DECT) and the PSTN (ISDN, CAS, DPNSS and analog) and also houses the DSP resources for handling tones, conferencing, packet switching towards IP Phones (SIP and H.323) and to convert media between different protocols. Furthermore, a new feature introduced with MX-ONE 5.0 enables the media gateway to run in software, meaning there is no need for dedicated media gateway hardware in IP only installations.
SYSTEM OVERVIEW When using Server redundancy, network redundancy must be installed, and bonding is the preferred option. Virtualization - With the advent of cloud computing technology, the cost of high availability, voice and data application hosting, content storage and service delivery will be reduced significantly. Cloud Computing broadens the horizons across organizational boundaries of "reusability of IT capabilities" which is the very fundamental principle in cloud computing.
MX-ONE SYSTEM DESCRIPTION SIP - has become the signaling protocol for establishing real-time multimedia communications. SIP is Key to Accelerating Unified Communications Deployments in an organization. Aastra has taken advantage of the fast developing SIP technology in the development of MX-ONE. MX-ONE SIP extension and SIP trunk are available today and will continue to evolve to provide a simpler migration path to Unified Communication.
SYSTEM OVERVIEW MX-ONE UC Solution enables activity and preference management that allow users to keep up-to-date quickly and efficiently on where they are, what device they are using and when and how they wish to be contacted. This allows employees in an organization to offer a personalized service to their customers.
MX-ONE SYSTEM DESCRIPTION prises. No business has to make compromises on how to process critical customer calls. Management Applications - Dealing with complexity in today's dynamic communication infrastructures is one the many challenges faced by IT managers and support staff.
SYSTEM OVERVIEW • • • • • An optional feature enabling full integration with major e-mail systems (Outlook, Lotus notes and Groupwise) with advanced plug-ins for VM management. A voice intercept messaging (VIM) option which allows integration with the MX-ONE message diversion feature as well as the CMG activity setting function. A TTS (text-to-speech) option that allows users to listen to their e-mails directly over the phone.
MX-ONE SYSTEM DESCRIPTION Solidus eCare is empowered with Mobile Extension for Aastra communication systems to equip remote or roaming. Customers can be guaranteed access to the most appropriate agent - wherever they are located and on whichever communications medium (i.e., voice, chat, e-mail, SMS, or fax) they prefer to use. Solidus eCare provides skills-based routing across these media, a single point of management and an integrated management information system across the contact center.
SYSTEM OVERVIEW • BluStar for PC • BluStar for iPad • BluStar for iPhone • AMC 4 clients (Presence and contact info) • BluStar Server System Architecture The BluStar clients are SIP based end-points with a rich set of UCC features that connects directly to the MX-ONE and the BluStar Server. Signaling and media rely on the device having data connectivity to an IP network and can operate on private or public IP networks.
MX-ONE SYSTEM DESCRIPTION 2.7 Collaboration Management Suite (CMG) Aastra Collaboration Management Suite (CMG) is a part of the UCC suite for MX-ONE. The CMG product portfolio provides a mix of communication tools for attendants and office users, including advanced call handling, activity and availability management as well as speech services.
SYSTEM OVERVIEW 2.7.1 BluStar Web With the release of MX-ONE 5.0 SP4 a new generation of the Collaboration Management Suite is introduced, The main components of this new offer consist of a completely new HTML5 based user interface and the CMG call routing and directory services have been modernized. It also offer full integration with the BluStar Server to offer rich presence services to BluStar Web users. Aastra BluStar Web is a set of services that enables business user to manage day-to-day activities.
MX-ONE SYSTEM DESCRIPTION • Complements the Aastra BluStar Ecosystem to enrich Aastra’s UC collaboration offering • MS Lync ready via BluStar Server integration • License model harmonized with Aastra’s standard licensing system • Please refer to CMG CPI documentation for further information 2.8 MX-ONE Management Applications 2.8.
SYSTEM OVERVIEW 2.8.2 MX-ONE Manager provisioning MX-ONE Manager Provisioning also provides functionality: • • • • • • Managing administrator accounts Adding subsystems, for example, MX-ONE Telephony Servers and CMG servers. Importing and exporting user and extension data Performing backup of user and extension data User account administration, for example, unlocking users. End-user self-service. Figure 5: Manager Provisioning For more details, see the description for MANAGER PROVISIONING. 2.8.
MX-ONE SYSTEM DESCRIPTION 2.8.4 MX-ONE Manager Availability MX-ONE Manager Availability provides fault and performance management for MX-ONE servers and applications, that is, MX-ONE Telephony System, OneBox as well as the Linux and Microsoft Windows servers they run on.
WHAT'S NEW IN MX-ONE 5.0 3.2 Virtualization The MX-ONE 5.0 solution release extends to support larger customer multi-server environments, offers hardware consolidation and enhanced resiliency options and is aimed at customers who have a company-wide virtualization strategy for all IS/IT based applications.
MX-ONE SYSTEM DESCRIPTION tered to only one directory number. As an example, it would be possible to have one directory number with three SIP end-points and one mobile extension assigned. From the licensing perspective, the user would need one SIP user license and one mobile extension license, and up to three additional device licenses, a total amount of five licenses. 3.
WHAT'S NEW IN MX-ONE 5.0 3.6 SIP trunk connection to Aastra Connectivity Server (ACS) As of MX-ONE V.4.1 SP4, the SIP connection towards ACS was changed to a SIP trunk connection, rather than using a remote SIP extension, as was the case previously. This change also applies to MX-ONE 5.0. Furthermore, with MX-ONE 5.0 some net services are now available for this SIP trunk connection between MX-ONE and ACS to enable certain feature interactions between MX-ONE and the InAttend attendant suite.
MX-ONE SYSTEM DESCRIPTION OneBox Unified Messaging: • One Box 5.0 SP3 SU3 • OneBox 5.1 CMG Server: • CMG Server 7.5 SP4 CMG BluStar Web 8.0 AMC: • AMC 4.0 • AMC 4.1 SIP DECT: 3.8.2 • OMM 3.1 • OMM 4.0 Active Directory and Mapping of User-Defined Fields Since previously, Manager Provisioning can automatically import user records from Active Directory. Values of user attributes in Active Directory are copied to the Manager Provisioning user records.
WHAT'S NEW IN MX-ONE 5.0 • 3.10 PostgreSQL 8.1 (included with the Manager Provisioning media kit) MX-ONE Manager System Performance Manager System Performance (MSP) 1.1 is a new application, part of the MX-ONE Management Suite. It provides simplified measurement and analysis of performance data from MX-ONE. MSP also gives the MX-ONE administrator information about the overall performance of trunks, routes, operators, individual extensions and common system resources. 3.10.
MX-ONE SYSTEM DESCRIPTION • • • Caller identification, enhanced information of incoming calls entries in the Busy Lamp Field Configure favorites for the WebPanel Timezone support For further information, refer to the product documentation and release notes available on the Aastra knowledge base. 3.12 BluStar Server Aastra presence engine, The BluStar Server, is an integral part of the MX-ONE 5.0 Solution. As of MX-ONE 5.
WHAT'S NEW IN MX-ONE 5.0 3.14 BluStar for iPad & iPhone Aastra BluStar for iOS 3.0.4 delivers high-quality audio and HD video as well as access to a set of UC features from a single client on the users iPad and iPhone. Following features are delivered in BluStar for iOS 3.0.
MX-ONE SYSTEM DESCRIPTION Note: When using a BluStar 8000i with MX-ONE Telephony System, a video license is necessary, per user. 3.15.2 BluStar for Conference Room The Aastra BluStar™ for Conference Room is a flexible video conferencing tool that is designed to enhance the way you communicate and collaborate.
WHAT'S NEW IN MX-ONE 5.0 3.15.4 Aastra 340w WiFi phones On top of MX-ONE 5.0 the WiFi phones Aastra 340w and Aastra 342w, including complementary accessories has been made available. The Aastra 342w is basically the same as the Aastra 340w but enhanced with a bar-code reader for 1d and 2d bar-codes. The phones are designed for application integration and fit segments like hospitals, logistics, warehouses and light industries.
MX-ONE SYSTEM DESCRIPTION • New range of base stations, supporting CATiq, GBit Ethernet and an interface for USB devices (RFP 35, 36, 37) • Combo base station - DECT CATiq and Wi-Fi (IEEE 802.11a,b,g,n) (RFP 43) No external antennas, ideal hotel solution • Aastra XML interface enabling tighter integration with MX-ONE to offer an improved end-user experience • New Aastra 650c CATiq DECT handset with wideband audio codec (G.
WHAT'S NEW IN MX-ONE 5.0 like agent actions, which consist in popping up a Web page or launching an executable when a call or session is presented to an agent. This can be a link to a CRM application, customer data, a map etc. Web pages can be shown either in the default browser or in “custom browser tabs”, i.e. directly inside the BluStar Agent application: Figure 8: BluStar Agent • Solidus eCare can manage a new type of media, named “Open Media”.
MX-ONE SYSTEM DESCRIPTION Figure 9: Interference with other media • A new type of outbound campaigns has been added: Progressive campaigns. Progressive campaigns consist in dialing numbers automatically before reserving an agent. This saves precious time for agents who don’t need to cope anymore with unanswered or busy calls anymore. • The outbound Campaign module has also been completely renewed in order to offer more customization possibilities and better management flexibility.
WHAT'S NEW IN MX-ONE 5.0 easily migrate from a competitor product to Solidus eCare, as it will be able to reuse its existing IVR application. (No need to re-develop IVR scripts anymore.) • 3.17 Finally, another new API has been added: Session Information Service. This API al-lows any third-party application being notified of each session that enters or leaves the queue, whatever its media (voice inbound, campaigns, e-mails, Open Media etc.).
MX-ONE SYSTEM DESCRIPTION • 3.19 BluStar Server based presence integration enabling the user to read and set status information. Supported by Android and iOs. (AMC4.1). OneBox- Unified Messaging With the release of MX-ONE 5.0 SP4, integration with OneBox 5.1 is introduced. This version is a dot release package and brings some enhancements primarily in the OneBox mobile client side. Please refer to the OneBox CPI documentation for a list of enhancements.
TELEPHONY FEATURES manager can see the status (free, ringing, parked, or busy) of each others phones, indicated by a Light Emitting Diode (LED). The manager or secretary can also use the programmed monitoring key to call the monitored party. Many configurations can be formed where individual secretaries can monitor the phones of one or more managers, as described in the figure below.
MX-ONE SYSTEM DESCRIPTION For more information, see the operational directions for Multi Terminal Service. 4.1.3 Personal Number A Personal Number is an extension directory number with a terminal of any type (not ISDN S0) assigned, providing system users (voice extensions) with different possible answering positions for the incoming calls. Every personal number can have up to five lists where each list can contain up to ten different answering positions.
TELEPHONY FEATURES Management (CMG) application suite and hard consoles (OPIs) can still be used. Calls are distributed among the active attendants. If there are no free attendants available, the calls are placed in queue. A queued call is distributed as soon as an attendant is available. The attendant functionality is provided by a separate server, the Aastra Connectivity Server (ACS). The ACS is connected with SIP to the MX-ONE Telephony System. The ACS provides queuing and call distribution.
MX-ONE SYSTEM DESCRIPTION extension can temporarily withdraw from the group by activating Follow-me to its own phone. Calls to a group from which all members have excluded themselves are diverted to the group's diverted position. 4.3.3 Group Do Not Disturb It is possible to form groups of users that during certain periods must not be disturbed.
TELEPHONY FEATURES one signaling system to another. Connections using ISDN and H.323 signaling systems are considered a homogeneous network. Systems 1 to 4 in the below figure are connected to each other using IP networking (H.323 with additional proprietary signaling). Systems 5 and 6 are connected to the network through leased lines using ISDN with QSIG signaling. All systems can have their own incoming and outgoing external lines to the PSTN.
MX-ONE SYSTEM DESCRIPTION attendant Remote MX-ONE Central site MX-ONE Attendant Attendant attendant Figure 13:Centralized attendant 4.4.2 Least Cost Routing The Least Cost Routing (LCR) feature enables MX-ONE Telephony System to select the most economical route for an outgoing public call. The system checks the dialed number to see if the private network can be used, and if that is the case, the call is routed to a PBX within the private network as close to the public destination as possible.
TELEPHONY FEATURES connections in that route are unavailable, the system tries to connect to system 3 through system 2 (alternative 2). Figure 14:Alternative Routing 4.4.4 Network Features In MX-ONE Telephony System, a number of common network features are supported. Typical network features are diversion, callback, intrusion, and call waiting (call offer). To use the network features fully, it is necessary to have a signaling system that can convey the necessary information.
MX-ONE SYSTEM DESCRIPTION 4.5.2 Functionality An MX-ONE Telephony System can serve end users belonging to different departments within an enterprise, or basic hosting customers, that can be completely separated regarding certain services. For example Call Discrimination can force the extensions to use routes/trunks to reach a user in another department (customer). A maximum of 250 departments (customers) can be used.
TELEPHONY FEATURES • • • • 4.6 Customer-dependent day and night service position Customer-dependent route selection Common diversion positions Recorded announcements Hospitality The special Hospitality functions are provided for the Hospitality industry. The functions are provided within the following areas: guest check-in, guest rooms and Service quarters. The Hospitality functionality requires the Hospitality license in MX-ONE plus middle ware from Diavox Technologies.
MX-ONE SYSTEM DESCRIPTION 4.7 VoIP Recording With active VoIP recording, the recording system will order the terminal to make a copies of received and sent RTP or SRTP packets and forward those to the recorder, preferably as two logical streams where received and sent packets are separated. Certain features of advanced VoIP recording systems are dependant on the receipt of two separate voice streams. Recording policies are defined in the recording systems, i.e.
TELEPHONY FEATURES The types of calling or connected parties that receive RVAs are, generally speaking, external lines and extensions, with some exceptions. For example, for diversion, group hunting, Automatic Call Distribution (ACD), call to an operator or to an extension, voice announcement can be provided when the call has originated from an extension, from a public trunk line, or from a tie line.
MX-ONE SYSTEM DESCRIPTION 5 Solution Architecture The MX-ONE solution comprises MX-ONE Telephony System that provides call control and features for multi media sessions (e.g.
SOLUTION ARCHITECTURE MX-ONE, as all other communication servers, needs a high quality IP network, such as Ethernet, in order to operate and provide high quality communications. This IP network shall be designed according to the best practice in the market to accommodate high quality Real Time services over IP. MX-ONE Telephony System provides business class telephony features. It performs call control, call-signaling, media transcoding and conversion functions.
MX-ONE SYSTEM DESCRIPTION • Compact SM (2U combination of EMG and MX-ONE Server (ESU only))*****) Server Options 5.1.1.2 *) Only MX-ONE Classic, MX-ONE Lite, MX-ONE Slim and Soft Switch are available for new sales in MX-ONE 5.0. **) Media Gateway Classic with LSU-E only exists in systems upgraded from earlier versions of MX-ONE. ***) LBP23 only exists in systems migrated from TSW with duplicated control system to earlier versions of MX-ONE and thereafter upgraded to MX-ONE 5.0.
SOLUTION ARCHITECTURE 5.1.1.3 Servers and gateways supported in MX-ONE 5.
MX-ONE SYSTEM DESCRIPTION Server/Gateway combinations • One to fifteen media gateways can be connected to one standard server. • MX-ONE/ASU supports up to fifteen media gateways with a total of max. 4000 users. • MX-ONE/ASU Lite supports up to fifteen media gateways with a total of max. 1000 users. • MX-ONE/ESU only supports one media gateway, except for upgraded or migrated systems where it can support two media gateways.
SOLUTION ARCHITECTURE ASU ASU Lite (Board and Server) (Board and ASU Lite Server) Type of system HP/ DELL MX-ONE Classic (MGU) Traditional Yes Yes Yes Yes MX-ONE Slim Multi Yes No Yes (only Yes ASU Server) (only ASU Gateway 5.1.1.
MX-ONE SYSTEM DESCRIPTION With this flexible deployment approach, the capacity of a MX-ONE telephony system can be scaled from approximately 100 to several hundred thousand extensions in normal traffic conditions. In a large scale MX-ONE system deployment, the Servers and media gateways are interconnected via a high speed IP infrastructure. Each Telephony Server and its associated Media Gateways can work an an autonomous unit if contact with the rest of the system is lost.
SOLUTION ARCHITECTURE A remote gateway is usually referred to as a media gateway which belongs to a multi-gateway MX-ONE system (e.g. located in the main HQ site) but installed in a remote site without local server. It is a cost effective way to facilitate a remote MX-ONE node, for instance to build a branch node or to collapse a private network into a single system. Local PSTN access can be provided, but the configuration does not offer survivability.
MX-ONE SYSTEM DESCRIPTION • To enable the emergency call service, procedures described in relevant operational directions must be followed carefully. It may not be possible to provide fully transparent services depending on the terminal types to dial the emergency number and the route access code defined to locate the right emergency center. For more details, refer to Operational Directions for Emergency Calls, SOS Calls. Considering the issues listed above, a remote MX-ONE unit (i.e.
SOLUTION ARCHITECTURE establishes the media connection between media gateways. The group switch is built up by Group Switch Modules (GSM). Each GSM can have 31 PCM lines connected to it. A group switch can have up to 8 GSMs, and it can be duplicated. The group switch cannot be used in multiple media gateway systems. For more information, see MIGRATING TSW/MD110 TO MX-ONE 5.0. 5.1.3 Media Gateway MX-ONE Telephony System supports several types of media gateways.
MX-ONE SYSTEM DESCRIPTION 5.1.3.3 MX-ONE Classic The MX-ONE Classic media gateway is provided as one 7U high, 19-inch wide subrack with a number of board positions for different functions and interfaces. The MX-ONE Classic is based on the MGU board. The MX-ONE Classic can optionally be equipped with an ASU or ASU Lite. This media gateway has the same interfaces as the MX-ONE Lite but provides more slots for added functions (boards). 5.1.3.
SOLUTION ARCHITECTURE 5.1.3.5 MX-ONE Media Server in MX-ONE Soft switch As an alternative to the hardware based Media Gateways, MX-ONE 5.0 SP4 offers the MX-ONE Media Server. The MX-ONE Media Server has the same VoIP DSP capacity as the hardware based MGU board described above and offers the following features: • 256 DSP resources for ad-hoc 8 party conferences, RVA, DTMF detection and forced GW calls • DTMF senders/receivers, intended for mobile extensions over SIP trunks. • Fax relay T.
MX-ONE SYSTEM DESCRIPTION • Analog MoH input, e.g. no live announcement for Emergency notification In the case that the above functionality is needed, then a TMU board must be present with the MGU based MGW chassis. 5.1.5 Earlier versions of Media Gateway Hardware This chapter describes MX-ONE media gateways supported by MX-ONE 5.0 but not available for new deliveries. 5.1.5.
SOLUTION ARCHITECTURE The SIP extension functionality when used with the Aastra 6700i terminals is offering a higher level of end user services than the MX-ONE Office IP phones. The SIP trunk solution in MX-ONE offers limited call functionality including caller ID/name DTMF digit signaling, diversion and bypass functions.
MX-ONE SYSTEM DESCRIPTION The standard servers support multiple-gateway configuration, i.e. one server can serve more than 1 gateway. 5.1.7.2 MX-ONE Server MX-ONE server is a unit built on proprietary platform with form factor compatible to MX-ONE building practice, Stackable or 19" rack mountable chassis (1U, 3U or 7U). When the server board is mounted in 1U chassis, it is also called "stand-alone" MX-ONE server. MX-ONE server consists of ESU, ASU or ASU Lite.
SOLUTION ARCHITECTURE Server Type ESU ASU ASU Lite Processor Pentium-M 1.4 GHz Intel P8400 mobile CPU 2.26 GHz, Dual core Intel ATOM D525 1.
MX-ONE SYSTEM DESCRIPTION 5.1.10 Boards and Functions in MX-ONE Media Gateways This chapter gives a general description of functions provided by the following MX-ONE media gateways: (please note that MX-ONE Slim does not have any slots for device boards. Functionality realized with such boards are not applicable for MX-ONE Slim) • MX-ONE Lite • MX-ONE Slim • MX-ONE Classic • Media Gateway Classic equipped with LSU-E (not for new deliveries). This chapter is not valid for EMG. 5.1.10.
SOLUTION ARCHITECTURE ELU34 uses two signaling methods to send out this type of information, either DTMF tones or Frequency Shift Keying (FSK). 5.1.10.4 Analog Trunk Units Analog trunk units are provided with the TLU80 and TLU83 boards. The TLU80 board provides analog E&M and inband tone signaling. The TLU83 board provides analog loop and ground start signaling. Note! The TLU 80 can only be used in MX-ONE Classic, not in MX-ONE Lite due to backplane function. 5.1.10.
MX-ONE SYSTEM DESCRIPTION 5.1.10.8 Tone Receiver/Sender and Conference Functions The purpose of the tone receiver or sender function is to send out and receive tone messages, such as dial tone, busy tone, congestion tone and DTMF tones. The function is required for extensions, trunk calls and conference calls. The TMU provides the function of tone/DTMF receiver, tone/DTMF sender, and conference functions. The TMU can be initiated to handle A-law or mu-law PCM.
SOLUTION ARCHITECTURE 5.1.10.12 FTU At power failure or processor malfunctions, the FTU board connects up to eight preselected analog phones directly to the public telephone exchange (PSTN terminals) through analog trunk lines. Normally the analog phones are connected to the ELU terminals, and the PSTN terminals to TLU terminals on the FTU2 board. 5.1.10.13 VCU The Voice Compression Unit is used for the Dynamic Route Allocation feature.
MX-ONE SYSTEM DESCRIPTION purpose. The device processor on the IPLU is equipped with 128 MB RAM for program and data memory and a 512 KB FLASH PROM for the boot program. The application program is loaded from the on-board Compact Flash card. The application program can be downloaded from a web server to the board. The IPLU supports T.38 fax for inter-LIM connections and for media connections to SIP end points.
SOLUTION ARCHITECTURE The functions in MX-ONE Manager are in accordance with the Fault, Configuration, Accounting, Performance, and Security Management (FCAPS) paradigm. For more information, see the description for MX-ONE MANAGER APPLICATIONS, 5.2.1 MX-ONE Manager Telephony System MX-ONE Manager Telephony System is a web-based application, accessed using a web browser.
MX-ONE SYSTEM DESCRIPTION When changing user and extension data in MX-ONE Manager Provisioning the corresponding data in the MX-ONE Telephony System, OneBox, and CMG databases is automatically updated accordingly. Note: The MX-ONE Manager Provisioning database is the master user and extension database in MX-ONE. MX-ONE Manager Provisioning must therefore be used when, for example, adding or deleting users.
SOLUTION ARCHITECTURE MSP supports extended reporting or radio base station performance statistics. Performance data can be easily accessed from the MX-ONE through the simple user interface. This data is automatically retrieved and stored in the MSP server. Using the Presentation Manager sub-modules, the data can be easily viewed, modified and presented in either report or graphic formats for printing or distribution within the organization.
MX-ONE SYSTEM DESCRIPTION the MX-ONE system, to the Calendar system (Exchange) and the directory server (CMG) and the BluStar end-points it can secure availability to the same set of directory and presence services independently of the type of BluStar device being used. For video and audio communication the BluStar clients are registered as Aastra SIP end-points to the MX-ONE system, supported by the MX-ONE managers.
SOLUTION ARCHITECTURE • • • • • • CMG BluStar Server core, including Directory Manager (web-based), Configuration Manager (web-based), Phone Book (tool for formatting and printing). Note that Directory Manager is used for managing CMG specific user data only. For detailed information regarding user data management, see 9.3 Configuration Management. InAttend and NOW, SIP-enabled PC-based attendant solutions.
MX-ONE SYSTEM DESCRIPTION 5.4 Terminals and User Applications The entry point for users of the MX-ONE is through the different clients. These clients can be either phones or software clients running as applications on PC’s or other devices. The different terminals and user devises connects to the MX-ONE server/gateway for their telephony services. For more information about the telephony functions for the different terminals and user equipment, see FEATURE LIST and CAPACITIES.
SOLUTION ARCHITECTURE 5.4.1 IP Phones In MX-ONE Telephony System, the IP phones can communicate using either the SIP or the H.323 protocol. Note that it is not recommended to use H.323 and SIP phones simultaneously in the same MX-ONE system. This is because calls between SIP and H.323 terminals will be forced gateway calls, which will lead to lower capacity as calls between the two versions will require gateway resources. Any SIP- or H.
MX-ONE SYSTEM DESCRIPTION FSK is supported for Caller ID. Rotary dialing phones only support basic call, they cannot use any additional services. For detailed information on analog phones, see directions for use for ANALOG EXTENSION FOR MX-ONE. 5.4.3 Analog Terminal Adapter Alternatively to connecting Analog devices directly to the analog extension interface, analog devices can also, locally as well as remotely, connect through a Terminal Adapter via SIP to the MX-ONE system.
SOLUTION ARCHITECTURE The mobile phone has access to functions and features comparable to an internal extension, such as callback and conference. Internal parties who call the mobile extension maintain full functions on such features as callback and camp on from operator. Additional phones can serve as alternate answering locations using a specific dialing procedure.
MX-ONE SYSTEM DESCRIPTION 5.4.7 IP DECT System The IP DECT system is based on the DECT GAP standard and integrates to MX-ONE via SIP, thus a SIP extension license is needed in MX-ONE for each DECT user. The handsets supported in the IP DECT system are the same as are use in the Integrated DECT system. The IP DECT system can be integrated with external applications such as different alarm systems, networks and e-mail.
SOLUTION ARCHITECTURE The Aastra 340w and Aastra 342w WiFi phones Connects to MX-ONE as any other Aastra SIP phone offering the users access to the same set of system services as from other Aastra SIP phones. 5.4.10 CAS Extension Interface The CAS extension interface provides a digital connection to external equipment and provides, through PCM links, the analog extension functions.
MX-ONE SYSTEM DESCRIPTION 5.4.13 Aastra Mobile Client (AMC) The Aastra Mobile Client (AMC) is a smart phone application that is integrated with MX-ONE Telephony System to provide Fixed Mobile Convergence. The client's Graphical User Interface gives the user easy access to the different functions of the Aastra MX-ONE exchange, e.g. short number, conference, call waiting and message diversion. Similar to if the user was accessing/using the features from its desk phone.
SOLUTION ARCHITECTURE 5.4.14 BluStar Clients The BluStar clients includes BluStar for PC, BluStar for iPad and BluStar for iPhone. These clients delivers high-quality audio and HD video as well as access to a set of UCC features from a single client on the user's desktop or iOS devise. The BluStar clients are registered in MX-ONE as Aastra SIP devices on the SIP/IP extension interface. License handling as well as user configuration is managed through the MX-ONE system tools.
MX-ONE SYSTEM DESCRIPTION 5.5 MX-ONE High Availability MX-ONE offers high availability by supporting the following types of redundancy in MX-ONE Telephony System: • Network redundancy, where two types are currently supported: – Dual subnet network redundancy (Not for new sales). This type of network redundancy is achieved (provided a redundant network infrastructure is available) by connecting Telephony Servers to two LANs.
SOLUTION ARCHITECTURE other one will continue to serve the operations and the Telephony Servers will be available on the functioning interface. Ethernet bonding is only supported in the Telephony Server Link Failover in the Media Gateway MGU A proprietary active/backup (link failover) network redundancy technique is used with the MGU in MX-ONE 4.1 SP1 and later releases.
MX-ONE SYSTEM DESCRIPTION HLR redundancy (Home Location Register redundancy), or HLR backup, is a unique MX-ONE feature for IP extensions based in the same concept of HLR/VLR (Home Location Register / Visitor Location Register) from Mobile networks. In a multi-server system it allows the possibility to register IP extensions with another Telephony Server (backup HLR), if the ordinary HLR server cannot be accessed. The feature is supported for H.323 and SIP extensions.
SOLUTION ARCHITECTURE server" should go down. This enables users to be able to register on another (visitor) server and work as usual. 5.6 Networking Capabilities Networking means to provide all services over network links to other entities of the Private Telephone Network (PTN). This cuts costs compared to the TDM-based leased line. Furthermore, it simplifies Branch Office scenarios to better fit the data network model with IP-connected Branch Offices.
MX-ONE SYSTEM DESCRIPTION 6 Telephony Server Software This chapter describes the MX-ONE Telephony Server software. 6.1 General The same Telephony Server software is used on any server. The software consists of the following parts: • • • • • 6.2 Linux operating system Service system Software acting as an interface between the telephony applications and the operating system. For more information, see section 6.4 Service System. Telephony applications Manager Telephony System (section 5.2.
TELEPHONY SERVER SOFTWARE System, data backup, license handling, system supervision, alarm handling, and automatic fault administration. A program unit as described in this document is the telephony term equivalent to the computing term "process", which is a running instance of a program, including all variables and other states. From this point on, only the term "program unit" will be used. A common function is a program unit that is centrally located and can be used by all program units in all servers.
MX-ONE SYSTEM DESCRIPTION the total number of servers that exists in the system, including their server numbers. 6.4.1.3 Server Status The server status function is used to keep and provide status information about all blocked or isolated servers. • Blocked server A server can be blocked manually from traffic or blocked by the system, if the server is faulty. Information about blocked servers is obtained by requesting status information for one or several servers.
TELEPHONY SERVER SOFTWARE 6.4.1.5 Hardware Configuration The hardware configuration function is used to give the following information relevant to device boards: • • • • • • Hardware position Board type Controlling program unit (if the board is initiated) Pointer to the controlling program unit Number of hardware individuals on the board (for example, number of supported extensions) Whether or not the board is blocked There are two types of device boards: physical and virtual.
MX-ONE SYSTEM DESCRIPTION 6.4.3 Functional Change The purpose of the functional change function is to carry out an update or upgrade, that is, to replace one or several program units in the system with new versions. The function includes the following actions: • Prepare the system for program unit change. Commands changing the reload data are prohibited during the duration of the functional change.
TELEPHONY SERVER SOFTWARE – Process ID and path to the executable file for new and old program unit versions 6.4.4 Start and Restart of MX-ONE Telephony System 6.4.4.1 System Start The purpose of the system start function is to set the system into operation after an update, upgrade or boot procedure. System start comprises two main functions: • • 6.4.4.2 Initial loading, which means that program units are loaded into memory.
MX-ONE SYSTEM DESCRIPTION Selected media gateway is restarted and all gateway calls will be stopped in the server. A manual restart is initiated by a command. It is not possible to change reload data, using commands during the restart phase. 6.4.5 Backup The purpose of the data backup function is to backup and restore exchange data. Data backup is initiated by a command or done periodically. If the backup fails, an alarm is sent.
TELEPHONY SERVER SOFTWARE The individual license is used for ports, for example, the analog extension. Each individual license is defined with a maximum number of allowed licenses. Any object that requires licensing seizes a license when the object is initiated. The license is released when the object is removed from the system. • System license The system license is used for optional system facilities, such as network services.
MX-ONE SYSTEM DESCRIPTION A distributed system solution implies that if a server fails, no traffic except traffic through this server will be disturbed. To avoid disturbances, no data lock up in other server should occur due to the faulty server. If a software connection between two servers is released only at one end, data areas will remain locked as long as the linkage to the area is lost. This can lead to a congestion situation.
TELEPHONY SERVER SOFTWARE Supervision of Voltage The purpose of the supervision of voltage function is to check the voltage of +5 V, -5 V, +12 V, -12 V, -48 V. When a fault occurs, an alarm is raised containing information about the relevant voltage and the location of the missing voltage. This function is only applicable for a Media Gateway Classic configuration.
MX-ONE SYSTEM DESCRIPTION – Signal entry in addressed program unit exists for the sent signal – Address control value correct If any fault is found, the signal is not executed and the job is discarded. The signal that caused any of the above errors is stored for manual fault investigation. Server/Gateway Disturbance Counter Each LIM has a disturbance counter that reflects the quality of the program execution in the LIM. The counter is incremented a number of steps each time a fault occurs.
TELEPHONY SERVER SOFTWARE Sequential tracing is used for tracing an activity. Through the sequential trace, the signals can be followed in their logical and chronological order and thus the chain of events that led to the fault. Sequential tracing should be used when the user has an idea of the activity that went wrong and wants to locate the break in the sequence. • Interface tracing Interface tracing is used to trace all signals to and from a program unit or a hardware equipment position.
MX-ONE SYSTEM DESCRIPTION 7 Interfaces and Protocols This section lists the external interfaces and protocols used in MX-ONE.
INTERFACES AND PROTOCOLS Figure 24:Interfaces and protocols in MX-ONE and MX-ONE Manager Figure 25:Interfaces and protocols in MX-ONE The following interfaces and protocols are available for MX-ONE Telephony System: • • Private networking by means of ISDN QSIG over E1 (30B+D) and T1 (23B+D), the latter only in MGU.
MX-ONE SYSTEM DESCRIPTION • • • • • • • • • • • • • • MFC CAS DASS2 CCS7 (Simplified TUP for China) Private networking by means of DPNSS and CAS over E1 (30B+D) and T1 (23B+D) Public ISDN over E1 (30B+D), T1 (23B+D) and BRI (2B+D) H.
MIGRATION • Messaging Applications Programming Interface (MAPI) The following interfaces and protocols are available for Manager Provisioning: • • • • Web Services XML HTTP HTTPS For detailed information about the different external interfaces and supported standards, see the description for MX-ONE SYSTEM PLANNING. 8 Migration MX-ONE supports migration of MD110/Telephony Switch to an MX-ONE 5.0 system.
MX-ONE SYSTEM DESCRIPTION 9 Operation and Maintenance 9.1 General Operation and maintenance in MX-ONE complies with the concept of Fault, Configuration, Accounting, Performance, and Security Management (FCAPS) for network management and consists of functions to supervise, administer, and manage the system. This chapter describes operation and maintenance in MX-ONE from an FCAPS perspective. 9.
OPERATION AND MAINTENANCE The alarm class 0 (cleared) is special. When the alarm sender notices that an alarm condition no longer exists, the sender will clear the alarm and the alarm class changes to 0. Alarm Generation The alarm classes (except alarm class 4) are assigned a limit for incremental alarm. This means that an incremental alarm is generated when a predetermined number of alarms with a certain alarm class have been stored in the alarm log.
MX-ONE SYSTEM DESCRIPTION Alarm Log If the alarm log becomes full, the alarms with the lowest alarm classes are removed from the log. A configuration parameter determines which alarms are least important. System Availability Alarms are not lost when the system is restarted. However, they are lost when the alarm feature is reloaded. After a reload, the feature will request are send of all alarms from the alarm sender. SNMP The Telephony Server has an alarm and event handling function.
OPERATION AND MAINTENANCE 9.3 Configuration Management This chapter describes how the MX-ONE components are used to configure MX-ONE. Data in MX-ONE can be divided into the following data types: • • • Telephony system data User and extension data Application specific data. Telephony system data is managed using MX-ONE Manager Telephony System and comprises data regarding, for example, server configurations, media gateways, number plans, and routes.
MX-ONE SYSTEM DESCRIPTION When managing user data in Manager Provisioning, the corresponding user data is automatically updated in the CMG SIP DECT and MX-ONE Telephony System databases. • Adding, changing and removing extensions When managing extension data in Manager Provisioning, the corresponding user data is automatically updated in the CMG, SIP DECT and MX-ONE Telephony System databases.
OPERATION AND MAINTENANCE 9.3.4 OneBox The following are some examples of data that is configurable for OneBox Fax Mail: • • • • Settings for fax support on the Telephony Server Global fax settings Inbound fax routing Notifications about document processing and server status For detailed information, see the getting started guide for Captaris RightFax and administrators guide for Captaris RightFax.
MX-ONE SYSTEM DESCRIPTION 9.4 • Configuration of connection to calendar system and to directory system • Presence handling Accounting Management Accounting Management comprises the services provided by MX-ONE that can be used for billing purposes. MX-ONE Telephony System generates customized Call Information Logging (CIL) records. Each record contains data for one call.
OPERATION AND MAINTENANCE Windows SNMP Agent, while other functions are embedded in the MX-ONE applications. For a short summary of the basic monitoring and performance management capabilities of the MX-ONE servers and applications, see section 9.6.1.1 MX-ONE Telephony System and 9.6.1.2 OneBox. 9.6.1.
MX-ONE SYSTEM DESCRIPTION 9.7.1 User Management In MX-ONE Telephony System it is possible to define the users that are allowed to use the Command Line Interface and the access privilege for each of them. 9.7.2 Audit and Security Trail The different components of MX-ONE log all activities that are relevant from the security point of view, such as access attempts, O&M operations, and so on. This information is necessary in case of a security incident to be able to determine what caused the event. 9.7.
SECURITY 10 Security Attention to the security aspects of an IP telephony infrastructure is increasingly growing by corporate Chief Information Officers (CIOs), IT administrators, and users. Voice over IP traffic (both signaling and media) must be protected from a number of attacks, for example, media streams eavesdropping, toll-fraud attacks, and signaling modification. For this reason, it is necessary to protect both the VoIP signaling messages as well as the media streams.
MX-ONE SYSTEM DESCRIPTION mechanism is available to assign users and administrators different roles and privileges. For detailed information about security, see the description for SECURITY.
CAPACITY 11 Capacity 11.1 MX-ONE Telephony System For information about the capacity of MX-ONE Telephony System configurations, see the description for CAPACITIES. 11.2 Non-virtualized environment Telephony Servers can also be delivered as software only together with media gateways. For this type of packaging, the functionality of the operating system including Linux support subscription and used server is the responsibility of the distributor.
MX-ONE SYSTEM DESCRIPTION Virtualized environment 11.3 For virtualized environment it is always recommended to follow VMware recommendations for host server configurations, but for running MX-ONE in a virtualized environment, the minimum configuration for the consolidated setup is the following: • Host machine hardware minimum for consolidation for 1 MX-ONE Telephony Server with maxi-mum 1000 users and 2 Calls/second using 0,2 Erlang as base.
CAPACITY Product users 11.5 No general guidelines as to how many users a 30-port system can handle, as fax usage varies greatly between customers. BluStar Server Table 4 BluStar Clients Product BluStar end-points supported by one BSS 11.6 1000 end-points SIP DECT Table 5 OneBox Voice Mail Product RFP’s in one system Up to 2.048 base stations DECT terminals in one system Up to 4.
MX-ONE SYSTEM DESCRIPTION 12 Environmental Conditions 12.1 General MX-ONE consists of different components as well as commercial server-based products. MX-ONE is designed to operate in and comply with regulations in force for enterprise (light industry) locations. Special measures may be required if MX-ONE is installed in other locations or if the environmental parameters deviate from the values described in this document or in other referenced documents. 12.
ENVIRONMENTAL CONDITIONS a. Recommend use odf SSD disk as storage media, if exposure to earth quakes is anticipated. Table 7 Mechanical Range Product Seismic exposure (product in operation) Transport VERTEQ II IEC 60068-2-6, -27, -64 and GR-63-CORE; ETSI EN 300-019-2-3 Class 3.2 Table 5 Random and bump IEC 60068-2-29, -32 and -64; ETSI 300 019-2-2 Class 2.2 Table 4 AC/DC power unit - stand-alone (not built-in) As specified by supplier As specified by supplier Limits for a non Aastra server, e.g.
MX-ONE SYSTEM DESCRIPTION 13 References The following SIP RFCs are supported by the MX-ONE Telephony System. E = Extension interface, T = Trunk interface. RFC 2246 2617 2833 2976 3261 3262 3263 3264 3265 3310 3311 3323 3325 3326 3398 3407 3428 3515 3550 3580 3581 3665 3680 3711 3725 3842 3891 114 Description Transport Layer Security (TLS) HTTP Authentication.
REFERENCES RFC 3892 3911 3960 3966 3986 4028 4040 4235 4244 4320 4346 4497 4566 (and 2327) 4568 4733 4904 4975 5168 5626 5627 5806 5850 6116 6140 6337 21/1551-ASP 113 01 Uen N2 2014-01-28 Description SIP Referred-by mechanism The SIP Join header Describes how to manage early media in SIP using two models: the gateway model and the application server model. Telephony Server supports the gateway model.
MX-ONE SYSTEM DESCRIPTION The following IP standards are also supported by the MX-ONE Telephony System: 116 ITU-T Recommendation Relevant G-series recommendations (G.107, G.108, G.109, G.111, G.114, G.131, G.168, G.175) ITU-T Recommendation Relevant P-series recommendations (P.800, P.862) ITU-T Recommendation Y.
