1. MX-ONE 5.0 Communication Server Pre-Sales Presentation (for existing Partners)

2. MX-ONE 5.0 – Highlights Virtualization Focus on SIP Unicode
SIP extension services
BluStar ecosystem
MSRP
Unicode
Group capacity
New hardware
Power savings
4/6/2017
EN/LZT RG

3. MX-ONE Virtualization

4. MX-ONE 5.0 Highlights Enterprise communications in the cloud
06/04/2017
MX-ONE 5.0 Highlights
Enterprise communications in the cloud
Infrastructure Consolidation and Centralization – IT focus today
Enhanced resilience and security in the cloud
Virtualization – cloud enabler while maintaining business continuity and user experience.
4/6/2017
EN/LZT RG

5. Virtualization of the Enterprise Communication
06/04/2017
Virtualization of the Enterprise Communication
Virtualization – cloud enabler while maintaining business continuity and user experience Enables new business models
Virtualization of UC Collaboration platform for SME
Leverage on LME offering to address SME segment
Virtualized Unified Communication Collaboration Appliance perfect fit for SME
UCC virtualized appliance on HP networking platform
Aastra 700
Infrastructure Consolidation and Centralization
Integrate to Information and Communication Technology (ICT) global strategy
Reduce server footprint and energy consumption, lower TCO
Migration to SIP trunking and network consolidation
Increased reliability of the total solution
MX-ONE
Virtualization ideal to offer large system UC capabilities to small organisations – proof point A700 – AllInOne - UC solution in a box
In Larger environments virtualization is a corporate strategy to reduce footprint/costs and simplify maintenance. Real time apps integrate in the same way as other IS/IT apps. Proof point MX-ONE and A5000
Virtualization as an enabler for organization to move away from CPE based implementation to private or public cloud
SaaS as a complement to move from CAPEX to OPEX
User on-demand services
Key Points of Cloud Definition
It’s not a single product…it’s a solution comprised of products
It’s not something different…it’s an extension of virtualization
Cloud Goals
Simplicity through further abstraction
Organization around consumers (Users) vs. providers
Further capital savings through economies of scale achieved by
Multi-tenancy
Efficient use of resources (use what you need, release what you don’t use)
Operational savings through
User self-service provisioning using standard catalogs
Financial transparency of costs through chargeback
Unified Communications and Collaboration to Desktop Virtualization
Desktop virtualization using VMware View offers IT tremendous benefits by moving desktops and applications into the cloud and delivering them as a managed service. IT administration is more automated and efficient, security is improved and the total cost of desktop ownership can be reduced by as much as 50 percent. End users can get a rich, consistent and high-performance desktop experience from any qualified device -- including mobile devices like tablets and smartphones -- whether in the
Move from CPE to the private or public cloud
On-demand services
Aastra Cloud concept
4/6/2017
EN/LZT RG

6. Virtualization – Consolidation & Centralization
06/04/2017
Virtualization – Consolidation & Centralization
Traditional communications environment
Separate servers for TS
Separate servers for UC applications
This slide only to emphasize what was said in the previous slide, so don’t hang on this slide for long ..
Basically, before virtualisation, you have different instances of the applications running on different servers. Takes up space and energy and requires a more complex maintenance process as they have to be handled individually. With virtualization in place, this situation will now change.
Click
VAN
4/6/2017
EN/LZT RG

7. Virtualization – Basic Setup
06/04/2017
Virtualization – Basic Setup
Virtualized Communications Servers
Virtualized Telephony Servers
Virtualized UC Applications Server
Benefits:
Consolidate TS and application servers
Reduce server footprint and facilitate data center management
Real time apps in line with company IS/IT virtualization strategy
This slide only to emphasize what was said in the previous slide
Main thing to point out is that both MX-ONE Call control management and UC/UM applications are now virtualized and can reside on the same host. Reduced footrpint/energy, fits well into corporate IT strategy: e.g. Fits perfectly into the Virtualization environment just like any other application for the IT department . Business as usual.
4/6/2017
EN/LZT RG 7

8. MX-ONE 5.0 Virtualization
Note
VMware is not provided by Aastra
VMware must be installed by certified partners/engineers
Basic setup, server consolidation without redundancy
Requires:
VMware vSphere, Hypervisor: ESXi 5.0
Basic setup, server consolidation using MX-ONE server redundancy
High Availability setups
Allows smooth upgrades with low downtimes
High Availability (HA)
Provides failover between servers with impact similar to MX-ONE Server Redundancy
Expected downtime reduced from around 5 minutes (n+1) to 30 to 60 seconds
No loss of LDAP master
High Availability (HA) + Fault Tolerance (FT)
Provides synchronized server duplication, a passive executes the same actions as the active
Provides full Hot-standby if an active server fails
SAN (Storage Area Networks) and a Network infrastructure according to VMware specifications
VMware vCenter
VMware vMotion
High Availability option
Fault Tolerance option
4/6/2017
EN/LZT RG

9. Virtualization – VMware High availability option
06/04/2017
Virtualization – VMware High availability option
Benefits
Warm standby solution
No Need for MX-ONE N+1 Redundancy
Direct media calls maintained
Valid for both Telephony Server and UC applications
HA Cluster
Telephony Servers V.5.0 guest machine running on top of VMware vSphere High Availability allows a warm standby solution, which means in the event that a physical server where the Telephony Server guest machine is running goes down, a downtime will happen due to the fact that Telephony Server guest machine needs to be initiated in another physical server. Although IP/SIP based direct media calls are maintained, during the initialization process ongoing media gateway (TDM) calls will be dropped.
The VMware High Availability setup can be compared with MX-ONE Server redundancy that uses Linux High Availability (HA), In case a customer has the VMware´s HA in place, MX-ONE Telephony System will be setup as a standard system. VMware does require that the necessary SAN and network infrastructure are in place.
The figure shows a standard MX-ONE Telephony System composed by four Telephony Server guest machines running on top of VMware´s HA infrastructure.
Click:
In case of host hardware failure or planned maintenance, the Telephony Servers guest machines running on top of the host machine are taken offline. The VMware HA mechanism will automatically initialize new instances of the same Telephony Servers guest machines in another available physical machine in the VMware´s HA cluster environment and the system is back in business. Typically, the outage is less than 2 minutes and all services are restored.
Benefits to point out:
This VMware option does not require any N+1 redundancy configuration in MX-ONE due to the fact that MX-ONE uses the High Availability provide by VMware.
Although this example focuses on the SUSE Linux call control VMs, this also applies for Aastra’s Windows 2008 based UC/UM applications.
VAN
Storage (iSCSI SAN)
4/6/2017
EN/LZT RG

10. Virtualization – Fault Tolerance option
06/04/2017
Virtualization – Fault Tolerance option
Benefits
Hot Standby - Server memory mirrored via dedicated LAN link
No down time or loss of calls / services
2 levels of back-up to offer true than ”5-nines” resilience
VMware
Fault
Tolerance
When Telephony Server guest machines are running in a VMware vSphere “Fault Tolerance” cluster, a transparent failover solution can be achieved. This means in the event that a physical server goes down, serivce is maintained and no calls will be dropped. The transparent failover is possible, according to VMware, because Fault Tolerance uses VMware vLockstep technology which guarantees the primary and secondary execute exactly the same x86 instruction sequences. Fault Tolerance requires that the hosts CPUs are compatible with vLockstep technology, including processor extensions. VMware requires that the SAN and appropriate parallel high speed network configurations are in place.
Simply put, when MX-ONE Telephony Server guest machines are running in one Vmware physical host, equivalent Telephony Server guest machines are also running in parallel in a second physical host executing the same instructions. As the guest machines are synchronised, in case the primary server fails or is shutdown (for maintenance) the second machine takes over seamlessly (matter of ms) and becomes the new primary host.
The figure below shows a standard MX-ONE Telephony System composed of 4 Telephony Server guest machines running on top of VMware´s FT infrastructure.
Click:
Therefore, when a failure in the primary server hardware happens, VMware´s FT mechanism in the secondary server will immediately notice it and it will take over starting to process pending I/O operations. The secondary machine will perform a “go live” operation and becomes the new primary. No service loss; no dropped calls. True hot standby is achieved.
As part of the recovery process, after the secondary machine successfully takes over, VMware´s FT process selects a new host machine within the cluster that has available resources and creates a new secondary host machine. After that, the system is protected again in case of a new hardware failure. This secondary process takes about one minute or the time to start up the VM and re-sync the x86 memory processes.
Proof point : Seeing is believing : propose them to see the Vmware FT demo we have in the demo hall during the breaks ..
HA/FT Cluster
VAN Very Fast Network
Storage (iSCSI SAN)
4/6/2017
EN/LZT RG

11. MX-ONE 5.0 virtualized - Benefits
06/04/2017
MX-ONE 5.0 virtualized - Benefits
IT Consolidation
Reduce capital costs
Infrastructure savings
Lower power consumption
Reduced cooling requirements
Decrease physical space requirements
Improve the efficiency and availability of IT resources
Increase Reliability
More reliable failover capabilities
Can achieve true ”5 nines” level of resilience
IT departments are more and more looking for alternatives to reduce the total cost of ownership and increase productivity, however in the last two decades, x86 architecture based servers have increased their numbers in the IT segment. Indeed, in a traditional x86 architecture only one or few applications share the same hardware. This meant the multiplication of servers which were each dedicated to a different back office applications (Mail servers, Web servers, Databases, CRM, etc.) to ensure enough resources to handle peak traffic. In most of the cases these applications do not use all the powerful of the server hardware and as a consequence causes waste of CPU, memory, etc. Additional servers, requires more power, cooling, physical space, maintenance, etc. which raises the TCO in data centers.
Virtualization software companies address such issues by offering possible ways to optimize server efficiency. For instance, this can be achieved by sharing hardware resources between virtual machines (guest machine).
Some of the benefits of this strategy are listed here.
There are some things to keep in mind when going for virtualization. Some examples are:
Network Complexity – mainly a requirement for more complex virtualization environments to enable decoupling of management and storage traffic from live traffic networks.
Hardware costs (SAN, etc..) – this is mainly required to allow things like Vmotion or high availability or fault tolerance, as the storage needs to be de-coupled form the host HW. It is a key component to simplifying maintenance of server and enabling seamless transport of virtual machines between hosts (maintenance, HA or failover, etc…)
Failover costs – there are fairly expensive SW options from virtualization vendors, but an organization’s need for increased reliability justifies the cost
Integrate to Information and Communication Technology (ICT) global strategy
4/6/2017
EN/LZT RG

12. MX-ONE SIP Extension Services

13. Enhanced Multiple Terminal Service
AKA Forking
Users with several terminals shall:
be able to have up to 4 active terminals (logged on)
actual maximum shall be set per user (existing functionality)
be able to have the same extension number
for log on to any of his/her terminals
if the user has an active terminal of the same type, it shall be forced logged-off
as dialled number to reach the user (on any of his/her terminals)
delivered as CLI from any of his/her terminals
have all active terminals ring simultaneously
4/6/2017
EN/LZT RG 13

14. Enhanced Multiple Terminal Service
Supported end user terminals, any choice up to a total of four
Arbitrary type of generic extension (DECT, virtual, H.323, 3rd party SIP, etc.)
But, only one of each type - note that just one single SIP terminal is permitted if it is a third party phone
Note that this is existing functionality with Forking
Desktop SIP terminal, 67xx or BluStar
BluStar for PC softphone
Remote extension over SIP e.g. a mobile with or without AMCC
SIP DECT
Selected end users may log on up to 4 identical desktop terminals
Controlled by user CoS
Note that call control and monitoring with CSTA is not supported
4/6/2017
EN/LZT RG 14

15. New MX-ONE Solution Licensing
06/04/2017
New MX-ONE Solution Licensing
MX-ONE Telephony Server 5.0
One extension license per directory number (analog, digital, CAS, ISDN S0)
One license per directory number (DECT, Mobile Extension)
One user license per directory number (IP)
The user license includes 1 device (SIP or H.323)
Up to 3 additional IP devices can be connected to the directory number This means that up to 4 IP devices (3 SIP and 1 H.323) can be registered to one directory number
Each extra IP terminal requires one terminal license
One SIP video media license per directory number
Upgrading, one IP extension gets one terminal
3:rd party SIP device
3:rd party SIP Device license (plus video media license to enable video for 3:rd party device)
BluStar for PC 2.0 (capabilities set per user in MX-ONE)
BluStar for PC client (New)
BSC CTI– no extension (New)
BSC softphone + video (New)
Additional options:
BSC Plug-in OSC/Lync (New)
BSC Plug-in IBM Sametime (New)
4/6/2017
EN/LZT RG 15

16. MX-ONE 5.0 Unicode Unicode is supported by MX-ONE and newer terminals
Aastra 6700i, 7xxx, 4223, 4225
Name and progress messages are supported
Managers (e.g. MP) can enter names in unicode
No translation of received/sent names
If Unicode is sent to terminals without support
Unicode ( F) cut to ASCII range (00-7F)
Characters outside sent as ?
Only English text files are created
Translation is the responsibility of the CSUs
4/6/2017
EN/LZT RG

17. MX-ONE 5.0 - SIP Extension Services
Shared call/line appearance
Supported only for the Aastra 6700i range of SIP terminals
Similar to MDN on DTSs
A line can be shared by several users
Monitor status of the shared line
Make and answer calls using the shared line from own telephone
Simple move of a call between sharing users
Call park pool
Any party can park a call against a call park pool number (individual or huntgroup)
The call park pool is configured with auto-park classified virtual SIPs ( )
User does transfer before answer to the call park pool
Parking party needs display to see which individual the call is parked against
So dont hang up too early
Any party can pick-up the call using individual call pick-up
If the parked call is not picked-up, the parking user, if generic, is recalled after 4 minutes (fixed)
4/6/2017
EN/LZT RG

18. MX-ONE 5.0 - SIP Extension Services
EDNs, Extra Directory Numbers (ADN phase 1) for Aastra 6700i phones
Similar to ADNs for DTSs
Can be defined on line keys 3 to 9 (if available on the terminal)
Automatically follows logon/off status of Line 1 (ODN)
Busy state is always individual for each line
If ODN is diverted or initiates DND
All EDNs are forced to DND
Note that DND for SIP is not the same service as the existing for e.g. ATS/DTS
4/6/2017
EN/LZT RG

19. MX-ONE 5.0 - SIP Extension Services
DND, Do Not Disturb
Individual and Group DND supported for A67xx
Same traffic functionality but different invokation
Treatment of calls to DND marked user/EDN can be configured
Number unobtainalbe tone
Skip own terminal in PN-list
Controlled distribution to remaining PN entries with DND-flag e.g.
For IDND
Direct to VM for internal calls
Direct to attendant for external calls
For GDND
Department nurses fixed phone
Department nurses DECT
IDND activated from own terminal or attendant
Bypass only from operator/attendant (*60#)
GDND activated from class marked extension
Bypass from operator/attendant, Master/GDND programming extension (*60#)
Automatic bypass for answer position
4/6/2017
EN/LZT RG

20. MX-ONE 5.0 – SIP Extension Services
Intercom for Aastra 6700i
Configured with EDNs, linked pair wise with hot-line
optionally auto answer set
Pressing the EDN-key, a hot-line call is set-up to the corresponding EDN
Signalled as internal call
No display updates until answered
With auto answer, the speech from the called phone is muted
Intercom can be configured to include DTS using ADNs
No muting by DTS
May work with third party SIP terminals
4/6/2017
EN/LZT RG

21. MX-ONE 5.0 - SIP Extension Services
Simulated individual diversion for Aastra 6700i
Not recommended for upgrading or migrating customers
Shall not be used for advanced users with e.g. Boss-Secretary, MNS, SCA, EDNs or several terminals
Provides a simple ”normal” divert feature by tweaking other services
Class marked extensions gets
One call list with no possibility to change or deactivate the list e.g.
Own extension
VM for internal calls
Attendant for external calls
A divert key and menu choices for diversion
* Procedures are not supported
Pressing the key or programming Follow-Me, ECF or Message Diversion
Active diversion is indicated on the phone
If key pressed or normal divert selected, phone is swtiched to DND mode
If two different diversions are active, the key has to be pressed twice
Manager Provisioning, simplified programming for most users
Divert template created in MP with ODN (the text) as first entry
Tick the ”simple divert” check-box
The users default call list is generated automatically
4/6/2017
EN/LZT RG

22. MX-ONE 5.0 - MSRP (RFC 4975) Message Session Relay Protocol (MSRP)
Primarily to support sending of IM between SIP end points
The session set-up is routed by MX-ONE
Uses the call list of the adressed person
Bypasses busy state
Distributed only to call list entries marked as MSRP capable
Only for internal sessions, not supported over SIP trunk
4/6/2017
EN/LZT RG

23. MX-ONE 5.0 - Feature Enhancements

24. MX-ONE 5.0 - Group Capacity
Expanded capacity for ACD/CTI/PBX groups (4.1 SP2 NPR)
ACD/CTI groups per server (from 32)
ACD/CTI groups per system (from 250)
Number of calls in queue, per server (from 1000)
Number of calls in queue, per system (from 1000)
Number of PBX groups per server (from 500)
MX-ONE 5.0 enhancements (NPR)
PBX hunt group members per server (from 1000)
PBX hunt groups per system (from 2500)
Call pick-up groups per server (from 75)
Call pick-up group members per server (from 1000)
Call pick-up group members per system (from 3600)
4/6/2017
EN/LZT RG

25. MX-ONE 5.0 - Miscellaneous Features
CAC enhancement
Will attempt to negotiate a lower bandwidth codec
CTI group as answer position in Call List (NPR)
Specify MGW for Operator Media Devices (OPERI)
Specify own Area Code for MGW (LCLDI)
Support for TR87, “CSTA 3 over SIP”
Enhanced SNMP
Agent parking of call in Supervisor silent Intrusion state (NPR)
Supervisor must request Silent Intrusion again during speech for the inquiry call.
A new CoS controls if Parking/Inquiry shall be permitted during intrusion
Agent (call handling with CTI-group) number presentation (4.1 SP4 NPR)
For calls via CTI group, a group class of service decides
Calls from, controlled by new procedure, *89*groupnumber#, #89#
Can be set with command extension_procedure -d abcde --proc "*89*abcde#"
The data is reload/static
abcde must be a defined CTI group
4/6/2017
EN/LZT RG

26. MX-ONE 5.0 - Miscellaneous Features
‘Contact Net Detector’ - Customer Identity via public ISDN trunk (NPR)
Transfer in Intrusion state (NPR)
Number log for DBC222 (NPR)
TLU83 A-number via DTMF signaling
ELU34, line ground supervision (block if grounded)
Support for QoS value ”Expedite Forwarding” (NPR)
MGU DTMF receivers connected in parallell
Improved integration with ACS/InAttend
Call history over SIP trunk (4.1 SP4)
Customer Identity over SIP trunk
Diversion bypass over SIP trunk
SOM enhancements
Conference, TCP/IP, Passive state timer, Multiple MGWs, Call Pick-up, Diversion enhancements, more error codes
4/6/2017
EN/LZT RG

27. MX-ONE Power Savings
Save over kWh per year if you have 1000 terminals
With 200 working days/year, 8 hours in the office per working day
Stand-by mode for A7444 and A7434
Individual by power-off key
Forced automatically by timer in config file
Display is black
Phone logged-off, calls will continue in the call list
PC port is off
Press power-on when you sit down at your desk in the morning
PIN required for security, i.e. phone is locked for unauthorized use
4/6/2017
EN/LZT RG

28. MX-ONE Terminals and Hardware

29. Introduced with MX-ONE 5.0
BluStar 8000i Desktop Media Phone
BluStar for PC 2.0
BluStar for iPad & iPhone (Q3)
Aastra 6735i, SIP phone w Gigabit (Q3)
Aastra 6737i, SIP phone w Gigabit (Q3)
(Aastra 650c, SIP DECT / CAT-iq)
Recently introduced:
Aastra 7100a
Aastra DT4x3
Aastra DT692
4/6/2017
EN/LZT RG

30. Aastra 6700i Series (SIP) Budget Functionality 6737i 6735i 6739i M675i
Expansion Module (3x20 progr. keys)
6757i
6755i
M670i
Expansion Module
(36 programmable keys)
6753i
6731i
6730i
4/6/2017
EN/LZT RG

31. New SIP phones
The 6735i and 6737i are new additions to Aastra’s Standards based SIP phone portfolio
These new models are upgraded versions of two existing models
Models are enhanced versions of our mid-range Standards-based SIP phones
6735i – is an upgraded version of the 6755i
6737i – is an upgraded version of the 6757i
Upgrades include
Dual Gigabit ports (versus dual 10/100 on existing models)
HD hardware – handset, speakerphone and headset jack
Increased power efficiency
4/6/2017
EN/LZT RG 31

32. BluStar 8000i Desktop Media Phone
06/04/2017
BluStar 8000i Desktop Media Phone
Dedicated and optimized desktop device
Superior usability
True HD video & audio
UC & business applications
Standards based, SIP & H.264
Integrated MX-ONE extension
Lower functionality than 67xx
True HD video conference and collaboration solution. Its way more than just a video phone (not to be positioned as low end video phone), which is why its called a “desktop media phone”.
4/6/2017
EN/LZT RG 32

33. UC 4 All – The collaboration client takes you to the next level
Aastra BluStar for PC
The new business collaboration client
A single user interface across:
Voice, video, directory/contact integration, IM, desktop sharing & conferencing
Means to find the right person, check the availability, collaborate using your preferred method
Collaboration from anywhere on any device & consistent user experience
Integration with Microsoft OCS/Lync & IBM Sametime, using plug-ins
Fully integrated with the Aastra MX-ONE call server
Provisioned as a multimedia end-point in MX-ONE
UC 4 All – The collaboration client takes you to the next level
4/6/2017
EN/LZT RG 33

34. UC 4 All – The collaboration client takes you to the next level
Aastra BluStar for PC 2.0
Aastra BluStar highlights
PC based SIP Softphone with HD voice
HD video (peer to peer)
Powerful audio processing
Instant Messaging
LDAP integration with global directory and integration with Personal Outlook Contacts:
Progressive directory search
Searches with local cache
Favorite list and grouping of favorite contacts
Click to call (“call to” links)
Remote access via Session Border Controller (External proxy for SBC)
Microsoft OCS/Lync and IBM Lotus Sametime plug-in integration
Enhanced functionality with Jabra and Plantronics headset
UC 4 All – The collaboration client takes you to the next level
4/6/2017
EN/LZT RG 34

35. SIP-DECT Release 3.0 Initial support of new RFP family
SIP-DECT 2.1 feature set with new RFP family
Mixed operation with old RFPs
CAT-iq 1.0 support
Support of the future 650c handset (not for NA)
New G.729 license for all types of RFPs
SIP-DECT XML Terminal API for Aastra 600d* / 650c handsets derived from the XML API for Aastra SIP Phones e.g.
To manage the redial list and call log
To manage the call forwarding indication, 1 display line in the idle display (e.g. presence state)
To run applications
* Requires 600d Release > 4.0
4/6/2017
EN/LZT RG

36. Handset features Generated by MX-ONE
Once registered with MX-ONE the 600c/d handsets will display the MX-ONE
user name
user number
user profile
info line
and
Use a new icon for call forward indication
4/6/2017
EN/LZT RG

37. Overview New RFP Models
Aastra‘s new RFP family
Supports CAT-iq high definition voice for our new high end 650c handset (EMEA + Australia, only)
G.722 support (G.723 support is discontinued)
Comes with a new powerful CPU for more performance: Marvell (Kirkwood) 88F6281 (1.2 GHz, L2 cache 256KB) This will enable additional future security features:
SRTP (RFC 3711) and secure SIP
Has a 1GBit Flash memory enabling local boot without a TFTP server. (All new RFPs will be delivered with a defined SIP-DECT software on board)
Is size and screw compatible with the old models
Supports 1GBit Ethernet
Supports the EU and the American DECT standards
4/6/2017
EN/LZT RG

38. MX-ONE New Hardware
Introduction of new version of the MGU with a 5 PPM clock
Introduction of ELU31/4 in ELU31/3 mode
Enhanced sync characteristics will be released in Service Packs to 5.0
With the aid of these enhanced boards, significant improvement of DECT synchronization can be achieved
No digital trunk connection required
4/6/2017
EN/LZT RG

39. MX-ONE Management Applications

40. MX-ONE 5.0 MP/MTS new functionality
Support for new MX-ONE 5.0 features
Support for Aastra 6737i and 6739i
BluStar 8000 video terminal deployment
Support for BluStar for PC
Support for ELU34/4
Load share/distribution of FW download for 6700i phones
Setting of HTTPS parameters for 6700i phones
AD field mapping on AD Search Domains
UDF mapping in AD
Accept * and # instead of A and B
Performance enhancements
Remember All selection as default in Extension list page
On the extension list page, list server number for generic extension
Improved EQU pos handling
Longer input fields for descriptions
MP support for ELU25
MP Web Services interface Document
4/6/2017
EN/LZT RG

41. Manager System Performance 1.0 - System management
Manages MX-ONE Performance data
Windows application for simplified measurements and analysis
Compatible with MX-ONE 4.1 and 5.0
Gathers and analyses Information about:
Trunks, Routes
Attendants
Extensions
Common resources
Graphical User Interface
Easy to read and customize traffic information
Traffic analysis of major MX-ONE components, including Radio Base Stations and IP extensions
Multiple MX-ONE nodes can be managed from a single Performance Manager application
Manager System Performance (MSP) provides simplified measurement and analysis of performance data from MX-ONE. It also gives the MX-ONE administrator information about the overall performance of trunks, routes, operators, individual extensions and common system resources.
4/6/2017
EN/LZT RG

42. MX-ONE Deployment

43. Centralized System with Remote Units (IP-PBX with Local Call Control) HQ and remote sites can also be multi-server/gateway w or w/o redundancy
ASU-E + MGU
TS 1 (Server)
WAN 2A 1A 1B
124A
ASU-E + MGU
Max 900 IP/ME or max 640
legacy users with ESU
4/6/2017
EN/LZT RG

44. Centralized Servers with Remote Media Gateways
100 ms roundtrip at 3 calls/sec
TS for MGU-based MGs
N+1 back-up
WAN
100 ms roundtrip
at 3 calls/sec
TS for LSU-E based MGs
Note: LSU-Es cannot be
automatically updated
with new software
100 ms roundtrip at 1.2 calls/sec
4/6/2017
EN/LZT RG

45. Inter Server Bandwidth (only the traffic dependant)
A very basic example with identical traffic patterns between all servers/gateways
TS 1 (server)
TS N
TS 2
SG = total number of Media Gateways in the system
OG= Own Media Gateways (2 for TS 1 and TS 2, 1 for TS N)
B/W= (SG-OG)/SG * 0.22 kbit/s * users per server
4/6/2017
EN/LZT RG

46. Bandwidth for a Remote Server
The very basic case assumes that the traffic interest is the same between all servers in the system, i.e. In a large system, all traffic is between servers and the internal case where A and B are handled by the same server is neglected.
1000 users with 0.2 E and standard holding times generates 1.7 calls per second. This corresponds to 220 kbit/s interserver signalling
Conclusion, each call generates 130 kbit data
For a remote server with 1000 users and 10% calls to the main site
1.7 calls per second total
0.17 calls to/from main site
Bandwidth for traffic to/from the remote server is then 0.17 calls/sec times 130kbit = 22 kbit/sec
4/6/2017
EN/LZT RG

47. Bandwidth Consumption, Remote Media Gateway
Result from a TDM-oriented measurement:
30 channels ISDN to 32 DTS, 2 calls/sec
9 kBytes from server, 4.5 kBytes to server
4/6/2017
EN/LZT RG

48. Summary

49. MX-ONE 5.0 Solutions Summary
06/04/2017
MX-ONE 5.0 Solutions Summary
Enterprise communications in the cloud
Infrastructure Consolidation and Centralization – IT focus today
Enhanced resilience and security in the cloud
Virtualization – cloud enabler while maintaining business continuity and user experience.
BluStar Ecosystem – Multimedia Collaboration
Aastra developments are addressing market trends
Aastra strategic direction for portfolio evolution
“BluStar” a common interface for consistent User Experience
Native SIP enhancements
Native Multimedia services for SIP users (Video and IM)
Integration of BluStar Eco-System
Multi-device licensing for SIP users
Focus on advanced features for Aastra SIP terminals
Strong integration with 3rd party products
IT & System Management
What’s new with Manager Provisioning
Manager System Performance
SNMP fault and alarms management
4/6/2017
EN/LZT RG

50. Thank you
Thank you
4/6/2017
EN/LZT RG