1 / 53

Mitel NuPoint Unified Messaging Release 4.2

morela
Download Presentation

Mitel NuPoint Unified Messaging Release 4.2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Mitel NuPoint Unified Messaging Release 4.2

    2. Agenda NuPoint Messenger Overview Mitel® NuPoint Messenger™ IP – Standard IP Mitel® NuPoint Messenger™ IP – 640E Mitel® NuPoint Messenger™ IP – 640IP Features (Renamed NuPoint Unified Messenger) Futures Question & Answer

    3. NuPoint Messenger - Overview Powerful, server based voice processing system Centralized, reliable and scalable messaging for the small, medium and large enterprises supporting: 100,000+ users Optional high reliability with Continuous System Operation Runs on a Mitel Standard Linux Operating System (MSL 9.1) that allows multi tasking, multi users, multi-platform and multi-threading Linux is an open standard operating system More reliable for real-time applications than Windows® For superior stability and security Three Models available: NuPoint Messenger IP – Standard Edition NuPoint Messenger IP – 640E aka Single Server 640 NuPoint Messenger IP – 640 IP aka Multi Server 640

    4. The NuPoint Messenger Stand-Alone Family NuPoint Messenger IP: Standard Edition 4 to 60 ports 960 Storage Hours 57,000 Mailboxes Hard Drive Redundancy NuPoint Messenger IP: Model 640 IP * Eight to 240 ports 10,000 Storage Hours 120,000 Mailboxes * Active/Passive CSO Software OR * Active/Active Eight to 480 ports

    5. NuPoint Unified Messaging Family

    6. NuPoint on MAS Differences from NuPoint Stand-Alone NP-UM on the MAS product does not support all the same features and functionality of the NP-UM standalone versions. The following standalone NP-UM features are not supported in the MAS NP-UM application: PMS Integration (Hospitality) NP TDD for the Hearing Impaired NP Audio Messaging Interchange Specification (AMIS) Third party non-Mitel PBX integrations (DMG/PMG gateway integration) Only Mitel MCD or Mitel 5000 CP integrations are supported High availability configurations, such as those available with the 640E and 640 platforms Greater than 2500 mailboxes/60 Ports (1000 mailboxes/32 Ports with vMAS) Competitive TUI Emulation NP-UM database backup only (with MAS you cannot back up and restore just the NP-UM database; you back up and restore the databases of all the MAS applications at the same time).

    7. NuPoint on MAS Differences from NuPoint Stand-Alone (Cont) Other Differences in NP-UM on MAS: NuPoint Unified Messaging is licensed on a per mailbox basis. Advanced UM Enablement License is included on MAS systems MAS comes with several languages available - any of which can be selected from the MAS system administrator interface, with some changes allowed by the user through the user portal. You do NOT set or select language from within NuPoint application when deployed as part of MAS. The languages are: English American British English UK French Canadian French Parisian Dutch Spanish LAM German (with MAS 2.2) Speech Auto Attendant is only supported for the following languages: North American English (NA) British English (UK) MAS is available as a software only, as a turnkey platform, and as a virtual application (see the MAS General Information Guide for details) MAS platforms can be deployed on the LAN or on the network edge (server-gateway mode)

    8. All Stand Alone Base Software Packages include: NuPoint Calling Line ID (NP CLID): NuPoint Messenger IP uses NP CLID to pick up inbound caller information and pass it to the user’s mailbox End of Warning Message (EMW): EMW alerts callers that they are running out of time to complete recording their message Extended Absence Greeting (EAG): EAG allows subscribers to set a vacation greeting which can be configured to redirect callers Numeric full set: Shipped as part of the base package, this is a North American English prompt set. It replaces the mnemonic prompts with numbers For example, “Press 7 to play your messages".

    9. Languages NuPoint Messenger IP is pre-configured to support two installed languages The default is North American English plus an additional language of your choice The maximum number of languages supported is 8

    10. LAN Back-up Available options: FTP server on the customer's LAN LAN backup using Microsoft Networking (mapped drive) LAN backup to USB memory stick Back-ups can be scheduled — daily, weekly, monthly Specific data can be selected for the backup or restore: System database Names Greetings Messages 480k per message Classes of Services

    11. NuPoint Messenger IP – Standard Edition Hardware Provided either as a software-only solution or as a bundled solution Software runs on the following certified servers available from Mitel: IBM x Series 3200 M3 HP ProLiant ML110 G5/G6* HP ProLiant DL320 G6 NP Redundancy option allows the system to automatically mirror information from the primary drive onto a secondary drive If either drive fails, the other drive contains the current configuration and any message and greeting data Software included at no charge Can upgrade to Model 640 IP* * Requires Hardware/Software migration

    12. Base Software Package - Standard Edition 8 to 60 ports Licensed for 8 8,000+ hours of message storage 57,000 Mailboxes Hard Drive Redundancy Corporate Call Director 50 licenses of Personal Call Director NP SMTP Forwarding and WebView (50 Sessions) NP SNMP NP CLI Web Console and Text Mode 2 Languages Mnemonic American English and Numeric full prompts included in base software LAN backup and restore

    13. NuPoint Messenger IP Model 640E (Single-Server) Hardware One HP DL 380 2U Rack Server with dual-core Xeon processor Six RAID 10 Redundant 146 GB Hard Drives (Two in RAID 1 for OS and four in RAID 10 for Message Storage) Dual NIC’s for load balancing and redundancy Redundant power / fans Available with internal RAID 10 only

    14. NuPoint Messenger IP - Model 640E Turnkey solution only Redundant Hardware Drives Six internal hard drives are used to store the operating system, mailboxes, applications and messages Power Supplies NIC Cards Fans In the event of a failure of non-critical nodes, the system would continue operate at reduced throughput, until the failing node would reboot. In case the active node fails, the critical processes float to another server, and call processing continuesIn the event of a failure of non-critical nodes, the system would continue operate at reduced throughput, until the failing node would reboot. In case the active node fails, the critical processes float to another server, and call processing continues

    15. Base Software Package – 640E Eight to 120 ports Licensed for 8 15,000+ hours of message storage 120,000 Mailboxes RAID 10 Hard Drive Redundancy Corporate Call Director 50 licenses of Personal Call Director NP SMTP Forwarding and WebView (60 Sessions) NP SNMP NP CLI Web Console and Text Mode 2 Languages Mnemonic American English and Numeric full prompts included in base software LAN backup and restore

    16. NuPoint Messenger IP Model 640 Hardware Two HP ProLiant DL360 G6 servers (dual processors) each with: Dual, embedded 1 Gigabit Network Interface Cards, the NICs provide voice connectivity as well as inter-server communication 6 GB RAM Redundant power supplies and redundant fans Xeon CPU, 3 GHz Two 250 GB hard drives, SATA, 7200 rpm One CD-ROM drive One diskette drive Two serial ports Two USB ports One MSA2000 SCSI disk array with seven SCSI drives (300 GB min) SCSI RAID storage for redundancy NAS/SAN Storage Optionally available

    17. NuPoint Messenger IP Model 640 IP Hardware Two HP ProLiant DL360 G6 1U Rack Servers with dual 3 GHz processors Redundant 250 GB Pluggable Hard Drive (RAID 1 for OS and NP Software) Dual NIC for load balancing and redundancy Redundant power / fans Shared External RAID with 7 x 300 GB hard drives (for NP configuration/user data, greetings and messages) and two hot swappable RAID Controllers

    18. Base Software Package – Model 640 IP Eight to 480* ports Licensed for 8 30,000+ hours of message storage 120,000 Mailboxes Redundant Servers Corporate Call Director 50 licenses of Personal Call Director NP SMTP Forwarding and WebView (60 Sessions minimum) NP SNMP NP CLI Web Console and Text Console 2 Languages Mnemonic American English and Numeric full prompts included in base software LAN backup and restore * Active/Active which may require NAS

    19. NuPoint Messenger IP - Model 640 IP External RAID10 Data Store (shared) Used to store all database information, user greetings and messages There are seven drives allowing for two to fail without disruption of service Continuous System Operation (Active/Passive) Provides resiliency ensuring that there is no single point of failure CSO uses a single server (Active server) to process all the services Additional server (Passive server) remains in standby mode The transition (fail-over) time from Passive to Active server is 30 seconds Upon failover, newly active server operates at full port capacity

    20. CSO Failover Scenarios SNMP alarm and error log generated when failure occurs Events that trigger failover to stand-by server Loss of Network Connectivity / Loss of both NICs Loss of both hard drives Failure of either CPU or motherboard Loss of both power supplies Loss of access to shared storage (external RAID) Critical software failure that restarts NuPoint Messenger will trigger failover For all failure scenarios described below, the SNMP alarms and error logs are generated when the failure occurs. 1. Non-fatal hardware failures on the active server – Common examples are: failure of a hard drive, failure of a NIC card, failure of a power supply. These failures do not trigger a fail-over from the active to the passive server. 2. Fatal failures on the active server – for example: total loss of network connectivity, losing two hard drives, losing power, and losing access to the shared storage. These conditions trigger the fail-over to the passive server. 3. Non-fatal software failures – for example: a non critical process crashed and it is restarted by the NPM master process. Non-Critical processes are the processes that are not related to the call processing. VPIM, NP Net, LAN Backup, PWG are all non critical applications. The services offered by all such processes will not be available until the PASSIVE server is made ACTIVE manually or the ACTIVE server fails, thus triggering the fail-over. 4. Fatal software failure – When a critical process crashes the NPM subsystem will restart it. In between the process restarts the call processing will be stopped. After the restart the call processing resumes immediately. If a process keeps crashing, the entire NPM system is brought down. These conditions trigger the fail-over to the standby server. The number of attempts the processes is spawned varies from process to process; for example SFA is restarted up to five times. Bad software will mean the both servers will keep crashing thus the ACTIVE processing will oscillate between servers. After 3 failovers within one hour, the system will be deemed unstable and will not start NPM anymore. The section on Hardware failure describes various hardware failures in brief. Hardware failure The following subsections describe the system behaviour when hardware components fail. Any type of hardware failures triggers an SNMP alarm and causes a message to be put in the error log. Also, if alarms are raised, these will be reflected in the System Alarms menu of both the text-based and web-based consoles. However, the audible alarms provided by the MCB II box are no longer available. Power supply outage on the servers and the disk array Each server as well as the disk array have redundant power supplies. If both power supplies of a server fail, that whole server fails. This results in a fail-over. If the power supplies of both servers fail, all service is lost. If both power supplies on the disk array fail, all service is lost. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. Fan outage Each server and the disk array have redundant fans installed. If one fan fails, the other one can provide adequate cooling for the system. Service is not affected. If both fans fail on a server, this results in that server shutting down. This causes a service failover to the passive server. If both fans fail on the disk array, the system goes down, causing loss of service. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. Disk drive outage on a server If one disk drive fails on a server, that server keeps working normally and an SNMP alarm is raised. This does not cause a fail-over. If both disks fail, the server is lost and a fail-over to the passive server occurs. When a failed drive is replaced, synching is done automatically by the RAID hardware. The drives are hot swappable, meaning that service is not affected when a drive is replaced. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. Disk drive outage on the disk array If one disk fails on the disk array, the system operation is not affected. The array controller is going to rebuild the contents of the failed disk on the spare disk. The disk array generates an SNMP alarm to signal the disk failure. During the rebuild operation, the system operates normally. The rebuild operation is completely transparent to the operating system and NPM. The RAID controller rebuilds the contents of the failed disk on the spare disk, using as source the mirror of the failed disk. If, during the rebuild operation, the mirror disk used for rebuild fails, the system will be down. If another disk fails other than the mirror disk used for rebuild, the system operates normally. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. SCSI RAID outage The disk array has two hot swappable internal SCSI controllers. If one of them fails, the other one can handle the disks. The switchover between the two controllers is transparent to the operating system and NPM. An SNMP alert is generated. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. If the ACTIVE server looses SCSI connectivity to the disk array, this will cause a fail-over. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. NIC outage The network traffic of each server is carried using the two teamed NICs. The teamed behaviour is handled by a software driver in the operating system. This driver splits the network traffic between the two NICs and also monitors them for failures. If one of the redundant NICs fails, the other NIC carries all the traffic. There is enough capacity in one NIC to handle all traffic. The failover operation from one card to the other is transparent to NPM. There is no interruption to service. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. CPU/Motherboard outage If either the CPU or the motherboard of a server fails, it takes down the entire server. This results in a fail-over. If the motherboards of both nodes fail, all service is lost. These failures generate SNMP alarms, but no logs in the NPM log. L2 switch or Router outage If a both the servers are connected to a single L2 switch or the router and if the L2 switch or router fails, the entire system is disconnected and no service is available. For increased system resiliency, we recommend connecting the two NICs on each server to different L2 switches. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. Precidia Ether232 outage The Precidia Ether232 box is not a redundant device. In the event that it dies, SMDI connectivity is lost. We will continue to look for a redundant alternative to this model. These failures generate no logs. SMDI connectivity can be provided using PIMG. Fail-over behaviour A fail-over occurs when the ACTIVE servers fails. The reasons for failure are described in the section above The PASSIVE server will become ACTIVE and will now handle all services. A fail-over is logged in the operating system’s log and in the cluster software’s log. When the passive server detects that the active server is down, it first stops any access to the shared storage. It then initiates the fencing of the failed node. This is a procedure by which the passive server makes sure that the failed server is power cycled. The fencing is done using the ILO interface. After the fencing operation succeeds, the passive node re-enables the access to the shared storage and then takes over the IP address of the cluster. It then starts all the services, becoming the active node. The failover is logged in the passive server’s log file and possibly the active server’s log file (if the active server did not crash). An SNMP alarm is also sent out to mark the moment when the failover is done. General Behaviour The following are behaviours during a fail-over. 1. Any live calls into the failed server at the time of failure are affected. The callers may experience a number of symptoms: 2. Re-order tone 3. Silence followed by re-order tone 4. Any web access to the failed server at the time of failure is affected. The users may experience: 5. Page time out if the passive system is not yet active. 6. If the passive system is now active the users will need to login again as their session data has been lost. 7. Any SMTP forwarding at the time of failure (UM basic and UM+MWI) is affected. The passive server retries the failed attempts when it becomes active. Thus the mail delivery is delayed. 8. If PIMG/TIMG integration is used and these devices do not busy out the trunks that correspond to the downed ports, calls can experience ring-no-answer until the PASSIVE server becomes ACTIVE. 9. If the downed ports are busied out (this is so with 3300 integration), calls get out-of-order treatment until PASSIVE server becomes ACTIVE. 10. Attempts to access the web server will experience a temporary outage. When the PASSIVE server takes over, it would have got the ACTIVE cluster’s IP address, hence the URL of the web server will stay the same. Users will be able to re-login after about 2 minutes from the start of the failover. 11. If the Ether232 box is used for SMDI, the newly ACTIVE server will now process SMDI data 12 If the Ether232 box is used for PMS, the newly ACTIVE server will now process PMS communication For all failure scenarios described below, the SNMP alarms and error logs are generated when the failure occurs. 1. Non-fatal hardware failures on the active server – Common examples are: failure of a hard drive, failure of a NIC card, failure of a power supply. These failures do not trigger a fail-over from the active to the passive server. 2. Fatal failures on the active server – for example: total loss of network connectivity, losing two hard drives, losing power, and losing access to the shared storage. These conditions trigger the fail-over to the passive server. 3. Non-fatal software failures – for example: a non critical process crashed and it is restarted by the NPM master process. Non-Critical processes are the processes that are not related to the call processing. VPIM, NP Net, LAN Backup, PWG are all non critical applications. The services offered by all such processes will not be available until the PASSIVE server is made ACTIVE manually or the ACTIVE server fails, thus triggering the fail-over. 4. Fatal software failure – When a critical process crashes the NPM subsystem will restart it. In between the process restarts the call processing will be stopped. After the restart the call processing resumes immediately. If a process keeps crashing, the entire NPM system is brought down. These conditions trigger the fail-over to the standby server. The number of attempts the processes is spawned varies from process to process; for example SFA is restarted up to five times. Bad software will mean the both servers will keep crashing thus the ACTIVE processing will oscillate between servers. After 3 failovers within one hour, the system will be deemed unstable and will not start NPM anymore. The section on Hardware failure describes various hardware failures in brief. Hardware failure The following subsections describe the system behaviour when hardware components fail. Any type of hardware failures triggers an SNMP alarm and causes a message to be put in the error log. Also, if alarms are raised, these will be reflected in the System Alarms menu of both the text-based and web-based consoles. However, the audible alarms provided by the MCB II box are no longer available. Power supply outage on the servers and the disk array Each server as well as the disk array have redundant power supplies. If both power supplies of a server fail, that whole server fails. This results in a fail-over. If the power supplies of both servers fail, all service is lost. If both power supplies on the disk array fail, all service is lost. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. Fan outage Each server and the disk array have redundant fans installed. If one fan fails, the other one can provide adequate cooling for the system. Service is not affected. If both fans fail on a server, this results in that server shutting down. This causes a service failover to the passive server. If both fans fail on the disk array, the system goes down, causing loss of service. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. Disk drive outage on a server If one disk drive fails on a server, that server keeps working normally and an SNMP alarm is raised. This does not cause a fail-over. If both disks fail, the server is lost and a fail-over to the passive server occurs. When a failed drive is replaced, synching is done automatically by the RAID hardware. The drives are hot swappable, meaning that service is not affected when a drive is replaced. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. Disk drive outage on the disk array If one disk fails on the disk array, the system operation is not affected. The array controller is going to rebuild the contents of the failed disk on the spare disk. The disk array generates an SNMP alarm to signal the disk failure. During the rebuild operation, the system operates normally. The rebuild operation is completely transparent to the operating system and NPM. The RAID controller rebuilds the contents of the failed disk on the spare disk, using as source the mirror of the failed disk. If, during the rebuild operation, the mirror disk used for rebuild fails, the system will be down. If another disk fails other than the mirror disk used for rebuild, the system operates normally. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. SCSI RAID outage The disk array has two hot swappable internal SCSI controllers. If one of them fails, the other one can handle the disks. The switchover between the two controllers is transparent to the operating system and NPM. An SNMP alert is generated. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. If the ACTIVE server looses SCSI connectivity to the disk array, this will cause a fail-over. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. NIC outage The network traffic of each server is carried using the two teamed NICs. The teamed behaviour is handled by a software driver in the operating system. This driver splits the network traffic between the two NICs and also monitors them for failures. If one of the redundant NICs fails, the other NIC carries all the traffic. There is enough capacity in one NIC to handle all traffic. The failover operation from one card to the other is transparent to NPM. There is no interruption to service. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. CPU/Motherboard outage If either the CPU or the motherboard of a server fails, it takes down the entire server. This results in a fail-over. If the motherboards of both nodes fail, all service is lost. These failures generate SNMP alarms, but no logs in the NPM log. L2 switch or Router outage If a both the servers are connected to a single L2 switch or the router and if the L2 switch or router fails, the entire system is disconnected and no service is available. For increased system resiliency, we recommend connecting the two NICs on each server to different L2 switches. These failures generate SNMP alarms, and the SNMP agent generates an entry in the NPM log. Precidia Ether232 outage The Precidia Ether232 box is not a redundant device. In the event that it dies, SMDI connectivity is lost. We will continue to look for a redundant alternative to this model. These failures generate no logs. SMDI connectivity can be provided using PIMG. Fail-over behaviour A fail-over occurs when the ACTIVE servers fails. The reasons for failure are described in the section above The PASSIVE server will become ACTIVE and will now handle all services. A fail-over is logged in the operating system’s log and in the cluster software’s log. When the passive server detects that the active server is down, it first stops any access to the shared storage. It then initiates the fencing of the failed node. This is a procedure by which the passive server makes sure that the failed server is power cycled. The fencing is done using the ILO interface. After the fencing operation succeeds, the passive node re-enables the access to the shared storage and then takes over the IP address of the cluster. It then starts all the services, becoming the active node. The failover is logged in the passive server’s log file and possibly the active server’s log file (if the active server did not crash). An SNMP alarm is also sent out to mark the moment when the failover is done. General Behaviour The following are behaviours during a fail-over. 1. Any live calls into the failed server at the time of failure are affected. The callers may experience a number of symptoms: 2. Re-order tone 3. Silence followed by re-order tone 4. Any web access to the failed server at the time of failure is affected. The users may experience: 5. Page time out if the passive system is not yet active. 6. If the passive system is now active the users will need to login again as their session data has been lost. 7. Any SMTP forwarding at the time of failure (UM basic and UM+MWI) is affected. The passive server retries the failed attempts when it becomes active. Thus the mail delivery is delayed. 8. If PIMG/TIMG integration is used and these devices do not busy out the trunks that correspond to the downed ports, calls can experience ring-no-answer until the PASSIVE server becomes ACTIVE. 9. If the downed ports are busied out (this is so with 3300 integration), calls get out-of-order treatment until PASSIVE server becomes ACTIVE. 10. Attempts to access the web server will experience a temporary outage. When the PASSIVE server takes over, it would have got the ACTIVE cluster’s IP address, hence the URL of the web server will stay the same. Users will be able to re-login after about 2 minutes from the start of the failover. 11. If the Ether232 box is used for SMDI, the newly ACTIVE server will now process SMDI data 12 If the Ether232 box is used for PMS, the newly ACTIVE server will now process PMS communication

    21. NuPoint Messenger – Model 640 IP Two Deployment Scenarios Active/Passive with SCSI Hard Disk Array Active/Active with SCSI Hard Disk Array Expanded Capacities with Active/Active Two times the port capacity Two times the port licensed features

    22. NuPoint Messenger IP Model 640 Deployments Active/Passive Key Points Single Site Collocated because of SCSI limitations All Ports integrated to one Server Failover with CSO

    23. NuPoint Messenger IP Model 640 Deployments Active/Active with MSA Key Points Single Site Collocated because of SCSI limitations Ports split between two Servers No CSO Failover available Active/Active Enablement License Required

    24. PBX Integrations

    25. Supported Integrations Mitel Networks SX-200 and SX-200 ICP SX-2000 3300 ICP Nortel Meridian (M-1 and SL-1) Norstar 8x24 and MICS Succession 3.0, 4.0, 4.5 & 5.0 Siemens Hicom 300E Hipath 4000 Lucent (Avaya) Definity G3 S8500 and S8700 NEC 2400 IMG 2400 IMX 2400 IPX NEAX 2000 IVS Hitachi HCX 5000 GTE Omni Fujitsu Starlog F9600 ESMDI (Central Office) Nortel DMS 100 Lucent 5ESS Nortel CS2100

    26. Enhanced SMDI Integration Software Up to 24 Enhanced Simplified Message Desk Interface (ESMDI)links per NuPoint IP system Uses Precidia IP to RS232 Devices for each link Used generally in a Central Office environment Multiple CO switches integrated into one NuPoint IP system Can be combined with another non-SMDI Integration Provides enhancements to the SMDI Integration Multiple SMDI-links (RS-232 links) 10 or 7 digits DN Faster link (9600 vs. 1200 baud in SMDI) Mailbox and extension mapping (Up to 16 Extensions per Mailbox)

    27. PBX-IP Media Gateway DMG-1000 aka (PIMG) The DMG provides integration from the NuPoint Messenger IP to the PBX and/or Central Office switch The DMG is an external peripheral that converts proprietary analog or digital PBX messages into Session Initiated Protocol (SIP) format for communication to the NuPoint Messenger IP Each DMG unit supports up to eight ports, one serial connection, and one LAN/WAN/private network connection A maximum of 15 DMG units can be used per NuPoint Messenger IP (Standard Edition) A maximum of 30 DMG units can be used per NuPoint Messenger IP (Model 640) Up to seven DMG’s can be installed in a rack mount unit

    28. Mitel Messaging T1/E1 Gateway The Mitel Messaging T1/E1 Gateway is used to deploy the NuPoint Messenger IP server in an E1/MSDN/QSIG or T1/MSDN/QSIG environment The T1/E1 Gateway connects to the integrated system (which can be either a Centrex or a PBX) using the embedded T1/E1 Module The NuPoint Messenger IP server communicates with the Gateway over IP NuPoint Messenger IP supports up to four Messaging Gateways

    29. NuPoint Messenger IP Integration to 3rd Party Switches with High-Capacity DMG-1000 units (aka PIMG’s) 19-Inch rack mount with 56 ports per Shelf (7 DMG’s) Support Digital / DSE and Analog / SMDI

    30. NuPoint Messenger 640 IP Multiple Switch Integration Overview

    31. NuPoint Unified Messenger Release 4.2 Features

    32. Simplified Management Support for Offline Installation Administrators Need not have Access to Text Based Console for Initial Provisioning New Wizard for Installation of NuPoint with 3300 Enhanced Web Console Passcode Aging: Ability to Force User to Change TUI Passcode Visual Tool-Tips for FCOS Options Commercial DB Support (PostgreSQL) Improved Database Integrity Database Backup Validation MBG Web Proxy Support for Internet Access Secure Public Internet "Roaming Access" via Mitel Border Gateway Advanced UM Offering with Teleworker and Mobile Extension Administrator Value with NuPoint UM 4.2

    33. Enhanced Personal Call Director Web-View and Online Help Enhanced Mobility Support Extended Support for Variety of Mobile Devices/Phones through Configurable Encoding Standard UM supported through MBG for Internet access without VPN Call-Back the Sender of Message from NuPoint UM TUI (3300 ICP MCD 4.0 and later) Enhanced Localization Support French Language Support for Speech AA and EAG (CDN and European French) LAM Spanish Support for Call Director System Prompts Advanced UM Support For Lotus Notes Version 7.0 (Blackberry, no plug-in) TTS Capacity Added to the System on a Per Channel Basis Advanced UM Licensed on a Per User Basis and Also as System Wide Enablement Option (Not New in 4.0) Ability for Administrator to Assign the Advanced Unified Messaging Capabilities on a Per Mailbox Basis Through FCOS Settings. Synchronize MWI on the Phone When Reading Messages Through Lotus Notes and Vise-Versa when the Message is Played Back Through the NuPoint TUI. MWI Synchronization Licensed with a System Wide Enablement Option User Value with NuPoint

    34. NuPoint UM, Key Takeaways Scalable & Carrier Grade Availability Platform at an Enterprise Price Point Feature Rich, Proven, Fully IP Messaging Platform with Mobility Support High Availability Architecture – No Single Point of Failure (Choice of Active/Passive or Active/Active Configurations) Heavily Leverages Open Standard Support for NAS Integration within the Data-Center Centralized Deployment Octel, Centigram and NuPoint Installed Base Migration Path Support for Multiple Concurrent Switch Integrations (Mitel 3300/5000 and Non-Mitel) Single Interface to Manage all Components / Networked Systems VPIM II and NP-Net Networking Support Lower TCO Linux Based “Single System” Solution for voice mail, unified messaging and speech Add Functionality / Capacity without Adding more Servers Optional Features are all Software Licensed – No Requirement for Hardware Upgrade/Additions

    35. Outbound Fax Support Using a Fax Driver Using Web-View Advanced Call Routing Tools Highly Flexible Call Director Capability for Advanced Call Management – Schedules, Custom Call Routing, Caller ID Filtering Administrator and User Configurable Via Web Interface Applications Portfolio Extended Benefits Microsoft® Office Live Communications Server 2007 Integration for Presence-Enabled call routing Mobility Solutions with Mitel Unified Communicator® (UC) Mobile NuPoint UM, Key Takeaways

    36. Standard UM with MWI support for Lotus Notes and GroupWise FCOS Configurable Voicemail Content in Email (Message Envelope only, Message Envelope + URL or Message Envelope + Encoded File) FCOS Configurable URL action (Launch Either Default Desktop Media Player, Web-View or Java Applet Player) Advanced UM Support for Lotus Notes 7 and Microsoft Exchange 2007/2010 Support for up to 500 users without the external MAPI/IMAP Server (Exchange) Support for up to 200 users using IMAP (Lotus Notes 7.0) Plug-in Support for Exchange Only Full Synchronization of MWI when Message played from URL and full content (Including TUI Actions or Direct E-Mail Deletion) using IMAP NuPoint UM, Key Takeaways

    37. NuPoint Unified Messenger

    38. Current Product Release Speech Enabled Automated Attendant Introduction Available as expansion to NuPoint OR Stand-Alone Speech Attendant Server Data Source can be: NuPoint Directory, Active Directory or MAS Text-to-Speech playback of non-recorded names Presence Announcements from OCS 2007 with Active Directory Source or Lotus Sametime 8.0 Key Points Supports up to 10,000 Names Supports up to 15 Departments Speech Tuning Available Database Backup is available The next release of NuPoint, release 11.0 is due in late calendar 2007. This release is focused on advanced unified messaging for Exchange 2003. Release 11 will offer: Text to speech: users will be able to have their e-mails read to them over the phone. This is particularly useful for your mobile users – they can listen to their e-mails when they are mobile and should be focusing their eyes on something other than their PC or Blackberry screen., such as when they are driving. This help improve efficiency and productivity as well, since employees can have deal with e-mail no matter where they are or what they are doing. For example, it allows employees to start their day when they get in their car for a 45 minute commute – getting productive right off the bat. Live Communications Server Integration: integration with Microsoft’s Live Communication Server, will give in the moment updates of the availability, location and user or device status for communicating. As well, greetings and call routing will be customizable based on your presence status, greatly improving your accessibility and responsiveness. The management of multiple NuPoints will be further simplified with the ability to manage a network of multiple NuPoints as a single image. Finally LDAP and Active Directory integration will create enhanced network integration and allow you to leverage your existing directory infrastructure. So before I move on to Messaging Server, I would just like to reiterate that NuPoint 10 offers functionality from basic voice mail to unified messaging and provides carrier scale and reliability at an enterprise price point.The next release of NuPoint, release 11.0 is due in late calendar 2007. This release is focused on advanced unified messaging for Exchange 2003. Release 11 will offer: Text to speech: users will be able to have their e-mails read to them over the phone. This is particularly useful for your mobile users – they can listen to their e-mails when they are mobile and should be focusing their eyes on something other than their PC or Blackberry screen., such as when they are driving. This help improve efficiency and productivity as well, since employees can have deal with e-mail no matter where they are or what they are doing. For example, it allows employees to start their day when they get in their car for a 45 minute commute – getting productive right off the bat. Live Communications Server Integration: integration with Microsoft’s Live Communication Server, will give in the moment updates of the availability, location and user or device status for communicating. As well, greetings and call routing will be customizable based on your presence status, greatly improving your accessibility and responsiveness. The management of multiple NuPoints will be further simplified with the ability to manage a network of multiple NuPoints as a single image. Finally LDAP and Active Directory integration will create enhanced network integration and allow you to leverage your existing directory infrastructure. So before I move on to Messaging Server, I would just like to reiterate that NuPoint 10 offers functionality from basic voice mail to unified messaging and provides carrier scale and reliability at an enterprise price point.

    39. Feature Content Advanced Unified Messaging Text-to-Speech playback of E-Mail Outbound Fax Uses Same SoftFax port licenses as Inbound Fax Licensed on a per user basis – No Initial Activation fee Uploading of .wav files for Call Director Professional recordings Microsoft Office Communicator tab Microsoft® Active Directory and LDAP integration Active Directory plug-in for creation / modification of mailboxes Support for Multiple Numbers Assigned to a single mailbox Extended Absence Greeting Ability to block mailbox from receiving messages Ability to block user from skipping greeting The next release of NuPoint, release 11.0 is due in late calendar 2007. This release is focused on advanced unified messaging for Exchange 2003. Release 11 will offer: Text to speech: users will be able to have their e-mails read to them over the phone. This is particularly useful for your mobile users – they can listen to their e-mails when they are mobile and should be focusing their eyes on something other than their PC or Blackberry screen., such as when they are driving. This help improve efficiency and productivity as well, since employees can have deal with e-mail no matter where they are or what they are doing. For example, it allows employees to start their day when they get in their car for a 45 minute commute – getting productive right off the bat. Live Communications Server Integration: integration with Microsoft’s Live Communication Server, will give in the moment updates of the availability, location and user or device status for communicating. As well, greetings and call routing will be customizable based on your presence status, greatly improving your accessibility and responsiveness. The management of multiple NuPoints will be further simplified with the ability to manage a network of multiple NuPoints as a single image. Finally LDAP and Active Directory integration will create enhanced network integration and allow you to leverage your existing directory infrastructure. So before I move on to Messaging Server, I would just like to reiterate that NuPoint 10 offers functionality from basic voice mail to unified messaging and provides carrier scale and reliability at an enterprise price point.The next release of NuPoint, release 11.0 is due in late calendar 2007. This release is focused on advanced unified messaging for Exchange 2003. Release 11 will offer: Text to speech: users will be able to have their e-mails read to them over the phone. This is particularly useful for your mobile users – they can listen to their e-mails when they are mobile and should be focusing their eyes on something other than their PC or Blackberry screen., such as when they are driving. This help improve efficiency and productivity as well, since employees can have deal with e-mail no matter where they are or what they are doing. For example, it allows employees to start their day when they get in their car for a 45 minute commute – getting productive right off the bat. Live Communications Server Integration: integration with Microsoft’s Live Communication Server, will give in the moment updates of the availability, location and user or device status for communicating. As well, greetings and call routing will be customizable based on your presence status, greatly improving your accessibility and responsiveness. The management of multiple NuPoints will be further simplified with the ability to manage a network of multiple NuPoints as a single image. Finally LDAP and Active Directory integration will create enhanced network integration and allow you to leverage your existing directory infrastructure. So before I move on to Messaging Server, I would just like to reiterate that NuPoint 10 offers functionality from basic voice mail to unified messaging and provides carrier scale and reliability at an enterprise price point.

    40. Unified Messaging – Standard SMTP Forwarding Included in Base Software

    41. Unified Messaging - Standard WebView 50-Sessions Included in Base Software

    42. NuPoint Messenger Advanced Unified Messaging With Microsoft Outlook / Exchange 2003/2007/2010 Voice / fax messages synchronized between NuPoint Messenger and Exchange 2003/2007/2010 Message Waiting Indication (MWI) on phone accurate regardless of method of access Outlook 2003/2007/2010 plug-in for integration of E-mail, voice mail and fax Voice message recording / playback on phone and PC multi-media device

    45. NuPoint IP Advanced Unified Messaging Advantages Duplicated Message Store in Exchange and NuPoint IP (Access to Voice Messages if Exchange Unavailable) Integration to Outlook/Exchange where Required Voicemail and E-mail Message Transport VPIM support For Networking Existing Disparate Voicemail Systems NP Net support for Networking Existing NuPoint Systems MiTAI/TDM/SIP Integration to Voice Infrastructure MWI support for Outlook and Non-Outlook Devices Voicemail TUI well established (Ability to emulate Octel) Speech Capabilities Through a Common Server Configuration FAX Support

    46. Unified Messaging – Standard UM

    47. Unified Messaging – Standard UM

    49. NuPoint IP Standard UM Advantages Single Message Store in NuPoint IP (Access to Voice Messages if email server is Unavailable) Integration certified to Outlook/Exchange, Lotus or GroupWise where Required Three E-mail addresses supported MWI support for Outlook and Non-Outlook E-mail Adheres to Sarbanes/Oxley Act

    50. Gain Control with Call Director! Most competitive feature that NuPoint Messenger has! Control how and when you are reached – improve your accessibility and improve customer service Web-based interface to create sophisticated call routing at the corporate auto attendant level and for individual users Route calls based on: Schedules Caller ID Multi level menus Includes Multiple greetings Screened and blind transfers Callbox Linking 50 Personal Call Director licenses Another key feature of NuPoint is Call Director, which gives your organization control over how calls are routed, and more importantly, gives your employees control over how and when they are reached, making them more accessible and better able to create work-life balance. Call Director is a web-based software application that allows both administrators and users to create Auto Attendant applications, and provides the ability to create voice menus for callers. Call Director is available as : Corporate Edition: works at the organizational line-group level to route calls and create auto attendant applications at the corporate level Personal Edition: works at the personal mailbox level, and gives users control over how and when calls reach them. With a personal auto-attendant and voice menu capabilities users can route calls and customize messages based on their schedule or who is calling. For example, Call Director can be set to route calls from specific callers such as important customers directly to a users cell phone, so they are always reachable to important callers. Also users can give their callers menus of options on how to reach them or another resource in the moment. For example, a user may give their caller the option to transfer to their cell phone to reach them immediately, or to transfer to another colleague if they are busy. Also consider the situation where you might be Another key feature of NuPoint is Call Director, which gives your organization control over how calls are routed, and more importantly, gives your employees control over how and when they are reached, making them more accessible and better able to create work-life balance. Call Director is a web-based software application that allows both administrators and users to create Auto Attendant applications, and provides the ability to create voice menus for callers. Call Director is available as : Corporate Edition: works at the organizational line-group level to route calls and create auto attendant applications at the corporate level Personal Edition: works at the personal mailbox level, and gives users control over how and when calls reach them. With a personal auto-attendant and voice menu capabilities users can route calls and customize messages based on their schedule or who is calling. For example, Call Director can be set to route calls from specific callers such as important customers directly to a users cell phone, so they are always reachable to important callers. Also users can give their callers menus of options on how to reach them or another resource in the moment. For example, a user may give their caller the option to transfer to their cell phone to reach them immediately, or to transfer to another colleague if they are busy. Also consider the situation where you might be

    51. Call Director Templates Create and save templates Admin controls what user has access to Ease of use (user) Ease of deployment (admin)

    52. Call Director - Continued Five Templates Provided out of the Box Personal Dial 0 Daily Greeting Alternate Daily Greeting Find Me Follow Me Call Director Reports Reports now can be generated for all the call flows and will be formatted in a way such that it will be easily printable

    53. Manage with Ease! Easy to use web-based management – minimizes training for administrators Manage multiple networked NuPoint Messenger systems from a common interface NuPoint is an easy to manage messaging solution that offers a web-based management console. You can manage multiple networked NuPoints from an intuitive GUI, that flattens the learning curve for new administrators. With the web-based management console you can Conduct Mailbox Maintenance: allows administrators to add, delete, modify and get mailbox information Generate Reports: generate billing, line usage and speech usage reports, that help you to understand how your system is being used. The billing reports are particularly useful to customers that do chargebacks for usage such as hotels, and organizations using activity based costing for internal charge backs. System Maintenance: allows administrators to perform cluster configuration and management of classes of service. Classes of service define the features and capabilities of a mailbox, by creating common classes of service that define the features for a particular type of user for example, a customer support employee or a sales employee – you can change the features available to a group of users simply by changing the class of service once, then that change will trickle down to all users with that class of service. This makes the management of large numbers of mailboxes much simpler, and minimizes the number of changes you need to make to the system. NuPoint is an easy to manage messaging solution that offers a web-based management console. You can manage multiple networked NuPoints from an intuitive GUI, that flattens the learning curve for new administrators. With the web-based management console you can Conduct Mailbox Maintenance: allows administrators to add, delete, modify and get mailbox information Generate Reports: generate billing, line usage and speech usage reports, that help you to understand how your system is being used. The billing reports are particularly useful to customers that do chargebacks for usage such as hotels, and organizations using activity based costing for internal charge backs. System Maintenance: allows administrators to perform cluster configuration and management of classes of service. Classes of service define the features and capabilities of a mailbox, by creating common classes of service that define the features for a particular type of user for example, a customer support employee or a sales employee – you can change the features available to a group of users simply by changing the class of service once, then that change will trickle down to all users with that class of service. This makes the management of large numbers of mailboxes much simpler, and minimizes the number of changes you need to make to the system.

    54. The next release of NuPoint, release 11.0 is due in late calendar 2007. This release is focused on advanced unified messaging for Exchange 2003. Release 11 will offer: Text to speech: users will be able to have their e-mails read to them over the phone. This is particularly useful for your mobile users – they can listen to their e-mails when they are mobile and should be focusing their eyes on something other than their PC or Blackberry screen., such as when they are driving. This help improve efficiency and productivity as well, since employees can have deal with e-mail no matter where they are or what they are doing. For example, it allows employees to start their day when they get in their car for a 45 minute commute – getting productive right off the bat. Live Communications Server Integration: integration with Microsoft’s Live Communication Server, will give in the moment updates of the availability, location and user or device status for communicating. As well, greetings and call routing will be customizable based on your presence status, greatly improving your accessibility and responsiveness. The management of multiple NuPoints will be further simplified with the ability to manage a network of multiple NuPoints as a single image. Finally LDAP and Active Directory integration will create enhanced network integration and allow you to leverage your existing directory infrastructure. So before I move on to Messaging Server, I would just like to reiterate that NuPoint 10 offers functionality from basic voice mail to unified messaging and provides carrier scale and reliability at an enterprise price point.The next release of NuPoint, release 11.0 is due in late calendar 2007. This release is focused on advanced unified messaging for Exchange 2003. Release 11 will offer: Text to speech: users will be able to have their e-mails read to them over the phone. This is particularly useful for your mobile users – they can listen to their e-mails when they are mobile and should be focusing their eyes on something other than their PC or Blackberry screen., such as when they are driving. This help improve efficiency and productivity as well, since employees can have deal with e-mail no matter where they are or what they are doing. For example, it allows employees to start their day when they get in their car for a 45 minute commute – getting productive right off the bat. Live Communications Server Integration: integration with Microsoft’s Live Communication Server, will give in the moment updates of the availability, location and user or device status for communicating. As well, greetings and call routing will be customizable based on your presence status, greatly improving your accessibility and responsiveness. The management of multiple NuPoints will be further simplified with the ability to manage a network of multiple NuPoints as a single image. Finally LDAP and Active Directory integration will create enhanced network integration and allow you to leverage your existing directory infrastructure. So before I move on to Messaging Server, I would just like to reiterate that NuPoint 10 offers functionality from basic voice mail to unified messaging and provides carrier scale and reliability at an enterprise price point.

More Related