OmniMessaging Functional Description OmniMessaging Functional Description Version 8.3 07/22/04 Opsol Integrators Inc.
OmniMessaging Functional Description 1 OMNIMESSAGING UMS SOLUTION OVERVIEW ................................................ 6 1.1 1.2 1.3 1.4 1.5 1.6 1.7 OMNI MMS ................................................................................................... 6 OMNI VOICE .................................................................................................. 7 OMNI IVR .................................................................................................... 7 OMNI ERS ............
OmniMessaging Functional Description 7.12 7.13 7.14 7.15 7.16 8 MAILBOX SELF-MANAGEMENT ......................................................................... AUTO DOWNLOAD OR CONFIRMATION OPTION........................................................ BRANDING ............................................................................................... NONSTOP RELIABILITY, SCALABILITY, AVAILABILITY................................................ CARRIER GRADE PERFORMANCE...............................
OmniMessaging Functional Description 11.3.2 Account Ownership ............................................................................ 11.3.3 Mail Users ........................................................................................ 11.4 MAILBOX MANAGEMENT................................................................................ 11.4.1 Mailbox Sharing ................................................................................ 11.4.2 Mailbox Maintenance By Administrator ..............
OmniMessaging Functional Description 21.9 22 F AULT T OLERANCE...................................................................................... 59 HARDWARE AND SOFTWARE COMPONENTS ................................................ 59 22.1 OMNI IVR CALL PROCESSING MODULE................................................................ 22.2 OMNI IVR CALL CONTROL MODULE.................................................................... 22.3 CALL F LOW PROGRAMMING .........................................
OmniMessaging Functional Description 1 OmniMessaging UMS Solution Overview Opsol’s OmniMessaging provides email, voice mail, short messages and Multi Media Messages for mobile operators, fixed line Telcos, ISPs and the enterprise. Banks use OmniMessaging to send emails from their Tandem applications. OmniMessaging is a high-performance messaging solution for environments that support tens of millions of subscribers.
OmniMessaging Functional Description OmniMessaging leverages the scalable HP NonStop™ platform so that extra capacity can be added as required: disks, processors and communications controllers can be added online, Message Store size is limited only by the size of the disk farm. Thus allowing Service Providers to cope with growth while the subscriber base is still connected. http://www.omnimms.com 1.
OmniMessaging Functional Description The target group can be a single street, a neighborhood or even a city. Organizations can broadcast alarms to all households in a radius of 5 miles from the disaster. The OmniERS database contains names, addresses, contact numbers as well as geographical information and location details. http://www.omniers.com 1.5 OmniMarketing The OmniMessaging Campaign Manager provides customer care via email and voice touch points.
OmniMessaging Functional Description the highest levels of availability, the lowest total cost of ownership, and adherence to open standards to integrate new applications and media formats. 1.
OmniMessaging Functional Description 3.
OmniMessaging Functional Description 5 OmniMessaging MMS, Email Opsol’s OmniMessaging provides an industrial-strength messaging solution suitable for electronic commerce and e-mail service providers, which demand scalability, reliability, and high-performance message backbones. OmniMessaging exploits the unique ability of HP NonStop™ systems to provide the most reliable email server in the world. OmniMessaging is reliable (99.999%), scalable and secure.
OmniMessaging Functional Description originator. If delivery of the NDR fails then the message is forwarded to an administrative mailbox and sends an alarm to the system console. 5.1.2 Scalable Email server OmniMessaging provides scalability in the following ways: • OmniMessaging components and processes can run in different processors on the same physical node. In addition you can cluster multiple nodes in a Multi node cluster to grow to a maximum of 4096 processors.
OmniMessaging Functional Description 5.1.4 Open System with conformance to Standards OmniMessaging uses and complies with Requests For Comments (RFCs), which are Internet standards used by the Internet community that apply to SMTP, MIME, TCP/IP, and DNS, among others. 5.1.5 Production ready operational environment OmniMessaging provides the following features that are essential to a commercial environment: • Detailed accounting and operational events.
OmniMessaging Functional Description SQL back-end, SASL, and replication support will be included in the next update. If you require SSL, you will need NSK-SSL for private key, certificate request and key generation. Features: Single threaded versions of the LDAP server. Test Suite included for install validation of LDAP server. LDIF tools - data conversion tools for use with slapd LDAP gateways - finger, gopher, email to LDAP gateways LDAP tools - A collection of command line LDAP utility programs 5.1.
OmniMessaging Functional Description • Facilities for configuration, management, accounting and statistical information. 6.2 Product Features Some of the product features are documented in this section 6.2.
OmniMessaging Functional Description 6.2.5 Security • POP Before SMTP Authentication • CRAM-MD5 Authentication • Configurable Max Login Attempts • Configurable Max Sessions Per User • Configurable Inactivity Timeout • Configurable Login Timeout • Encrypted passwords on the network • Access Control Lists on data files • BCC Header Deletion 6.2.6 Multi-Lingual Support • Quoted User Name Support • Configurable Non-Delivery Report Messages 6.2.
OmniMessaging Functional Description 7 Mobile OmniMessaging Features (To purchase this additional module please contact your HP Sales Representative) 7.1 MMS - Multi Media Messaging support The OmniMessaging solution includes a Multi Media Messaging server to provide text and graphics to a cell phone. Opsol provides the MMS server over two protocols. We use the Mobile IMAP protocol for speed, small cell phone footprint and conformance to standard protocols.
OmniMessaging Functional Description 7.5 IMAP, POP, SMTP Protocol support Users can access the OmniMessaging server using standard email clients (e.g. Microsoft Outlook Express, Netscape). The user configures zlemail.com as their SMTP server, IMAP server or POP server. Requests come in to the OmniMessaging server as standard TCPIP requests. The wireless access is provided by the Cellular Network Provider. 7.
OmniMessaging Functional Description 7.10 Workgroup Mailbox ISPs can offer workgroup mailboxes to corporate and individual customers on a group-sharing basis. A workgroup mailbox is similar to the concept of E-groups or knowledge sharing groups. Hence a member can subscribe to these groups, and exchange mails with members of the workgroup. 7.11 Information Subscription Users can subscribe to Subscriptions or information based on their requirements.
OmniMessaging Functional Description 8 Multi-Node Architecture Overview In a multi-node OmniMessaging system; the message store is partitioned into several HP NonStop™ nodes. The pop/imap/smtp request from outside can come to a server at any node. The recipient server will make sure that the message retrieval/storage occurs in the message store on the primary node that is assigned to the user/submission-address transparent to the client, whenever the primary node is up.
OmniMessaging Functional Description 7. The permanent storage for a user is always on his home node. Intermediate storage for new mails is provided on backup nodes. After maintenance of the users primary node is complete, the users mails will be transferred to the original home node. This action is scheduled by the operator. 07/22/04 Opsol Integrators Inc.
OmniMessaging Functional Description 9 HP NonStop™ Platform Requirements 9.1 Software Requirements The OmniMessaging product runs on the NonStop™ platform (K1000 plus) with the NonStop™ Kernel operating system version D47 or G06 and above. You must be connected to a TCP/IP network (Internet or local intranet) with access to a DNS server. NonStop™ Kernel Operating System G06.
OmniMessaging Functional Description 10 OmniMessaging Components OmniMessaging(tm) Architecture on Compaq NonStop(tm) Himalaya servers SNMP Alarms Billing Message Translation 2 3 Monitor Logs Perf & Stats Event Subsystem Application ManagerMessage Store APIs Embedded SQL Notification Content Parsing Notification Q Mailbox Maint Message Store Mailbox Aging to other clusters S 07/22/04 OpenSwitch Multi Node TCPIP Socket Distributor Directory Server User Profile Q Disc Q File Replicate Clu
OmniMessaging Functional Description 10.1 Provisioning Translator System – NAM, Listener, Users are provisioned on the system using the provisioning server. The following method can re are three interfaces • Java Provisioning client – PC based. The Java Administrator Client allows an Administrator to manage the entire configuration of the OmniMessaging application. It is portable and can execute on any system that supports Java. It is used to add domains, users, blacklists etc.
OmniMessaging Functional Description When a receiving MTA process receives a message that needs to be sent to a remote domain it passes this message to a sending MTA process to be relayed on. Since the neither the distributor nor the receiving MTA use Pathsend for dynamic load balancing, you must add additional receiving and sending MTA processes (using the OmniMessaging Application Manager) to increase the number of MTA server-class processes for increasing loads. 10.1.
OmniMessaging Functional Description If the delete operation fails, the MBM retries the failed operation as specified in the Max retry count entry. If retries are exhausted, the record is written to the MBM backup queue. The MBM will reschedule a message delete until all sessions that have the mailbox selected are aware that the message has been expunged. The MBM will reschedule a mailbox delete until there are no sessions that have the mailbox selected.
OmniMessaging Functional Description IMAP4 is an Internet Protocol (IP) for remote mailbox access; its specifications are documented in RFC 2060 (for more information, see RFC 2060—Internet Message Access Protocol - version 4rev1). Initially, the server host starts the IMAP4 service by monitoring TCP port 143. When a client host establishes a TCP connection with the server host, the IMAP4 server sends a greeting.
OmniMessaging Functional Description Message Transfer Agent servers (MTA): • # of current incoming sessions • # of current outgoing sessions • Send Q length • # of incoming sessions • # of messages received • # of receive recipients • # of outgoing sessions • # of messages sent • # of send recipients Local Delivery Server (LDS): • # of messages stored • # of messages rejected • # of messages w/NDRs • # of messages recipients • # of messages invalid recipient • # of messages expl
OmniMessaging Functional Description 10.1.12 LDAP3 interface / Directory Server (optional) The Directory Server provides user information for local OmniMessaging components via the Server class send APIs. Applications on other platforms desiring access to the OmniMessaging User profile can use a socket interface or an LDAP3 interface. The Directory Server runs as a NonStop™ TSMP Server class for persistence and scalability. LOCAL The figure below describes the flow for the directory server.
OmniMessaging Functional Description 10.1.13 Multi Node Directory Server The Directory server runs as a TSMP server class. The input is an email address (submission address) or User Name and the output is the users home node and backup node instances. A Programmatic Interface is provided for custom applications attempting to use the Directory Server.
OmniMessaging Functional Description up or the backup nodes process name if the home node is down. We currently support 2 backup nodes. A Programmatic Interface is provided for custom applications that need to use the OpenSwitch. 07/22/04 Opsol Integrators Inc.
OmniMessaging Functional Description 11 OMNIMESSAGING FEATURES 11.1 Mail Delivery 11.1.1 Message Broadcasting Message Broadcast is a mechanism that will allow a message to be delivered to ALL recipients at a given domain. An administrator sending a message to a special submission address triggers the process. OmniMessaging automatically expands the recipient list to include all users in the domain. Built in checks prevent this procedure from being abused by hackers. 11.1.
OmniMessaging Functional Description 11.1.4 Mail User Auto-Reply/Holiday Messaging OmniMessaging can be configured to send auto-reply messages sent to a particular mail address.
OmniMessaging Functional Description • Domain of sending MTA • SMTP From Address Each of the above can be blacklisted at the following levels:• System Level • Domain Level (the local recipient’s domain) Finally the system also allows SMTP From Address blacklisting at mailbox level. Domain Level and Mailbox Level spam checking can be activated or inactivated via system parameters (DOMAIN_LEVEL_SPAM_CHECKING, MAILBOX_LEVEL_SPAM_CHECKING) 11.1.
OmniMessaging Functional Description 11.1.9 Delivery Notification Interface OmniMessaging provides an optional delivery notification interface. This facility can be activated via a Service Package level parameter (DELIVERY_NOTIFICATION).
OmniMessaging Functional Description 11.2 Configurable Limits 11.2.1 Max Mailbox Size Max Mailbox Size limits are configurable at the following levels which are listed in order of usage, i.e.
OmniMessaging Functional Description periodically, a warning mail, indicating the mailbox is almost full with the percentage full, is also delivered to the recipient mailbox. Only one warning, either in response to an IMAP Append or Copy command warning or in response to an SMTP mail, will be generated within a configurable time period (WARN_MAIL_SEND_INTERVAL system parameter). It is possible to set the limits at each level to indicate no limit.
OmniMessaging Functional Description The Message Aging Server (MAS) uses this value to ascertain when messages can be deleted out of mailboxes. It is possible to set this limit to indicate that messages should be retained indefinitely. 11.2.5 Max Local Message Size Max Local Message Size is configurable at the following levels which are listed in order of usage, i.e.
OmniMessaging Functional Description 11.3 User Configuration ISP with Virtual Domains System Administrator ISP Account Manager for other corporates Corp1.com ISP Account Manager Opsol.com Managed by Domain Administrator Corp2.com Janette@Opsol.com Managed by Domain Administrator Some options managed by Janette Shared Folders Managed by Janette Small Account Manager Atul@Opsol.com Managed by Atul Martin@Opsol.com Managed by Martin user1@isp.
OmniMessaging Functional Description or IMAP4 protocol user or both. The Login User Name is a unique string that should not be confused with the submission address. A Submission address defines the local part of the email address (i.e. person’s name or job role ‘sales’, ‘personnel’ etc) and links this to the domain name. OmniMessaging uses the Login User Name to denote ownership of mailboxes. A user can thereby have many mailboxes and many submission addresses for mail delivery.
OmniMessaging Functional Description The MAS server can be configured to delete messages on a per user basis with the following options Messages older than a certain period Maximum number of messages in a mailbox Mailbox size exceeded 07/22/04 Opsol Integrators Inc.
OmniMessaging Functional Description 11.5 Security 11.5.1 POP Before SMTP Authentication OmniMessaging provides support for POP Before SMTP Authentication. This is an optional facility that is activated or deactivated by the POP_BEFORE_SMTP system parameter.
OmniMessaging Functional Description 11.5.6 Login Timeout OmniMessaging allows the configuration of a login timeout. For IMAP and POP sessions, if the user has not logged in successfully before the login timeout expires, then the session is terminated. The Login Timeout value is configured via the NSIM-IMAP-LOGON-TIMEOUT and NSIM-POP3-LOGON-TIMEOUT parameters for the IMAP and POP servers respectively. The value is specified in seconds. 11.5.
OmniMessaging Functional Description 11.5.10 Optional IMAP Login Failure Within OmniMessaging it is possible to configure how a failed login is handled. This is to allow for differences between different client types. There are two options:• Drop the session if the user fails authentication • Retain the session if the user fails authentication This is controlled by the system parameter AUTH_FAILED_KEEP_CONNECTION. 11.5.
OmniMessaging Functional Description 12 APPENDIX - System Parameters Parameter Descriptions The following table lists and describes all system parameters. Flags have values of either MSD_ACTIVE or MSD_INACTIVE.
OmniMessaging Functional Description Parameter Description MAX_SUBNET_CACHE MAX_SUBNET_KEEP_ PERIOD MAX_PARAMS_KEEP_ PERIOD MAX_WLIST_DOM_CACH E MAX_WLIST_DOM_KEEP _ PERIOD AUTOREPLY_INTERVAL WARN_MAIL_SEND_ INTERVAL DANGLING_MSG_KEEP_ PERIOD MAX_MBOX_PER_USER MAX_SUBSCRIPTION_ PER_USER MAX_LOGIN_ATTEMPTS MAX_SESSIONS_PER_ USER REMOVE_BCC_HEADER POP_BEFORE_SMTP POP_BEFORE_SMTP_ PERIOD MAX_REMOTE_MSG_ SIZE NDR_INCLUDE_ONLY_ HEADERS MAX_NUMBER_OF_ MESSAGES AUTH_FAILED_KEEP_ CONNECTION 07/22/04 Sect .
OmniMessaging Functional Description Parameter Description Sect . Ref. Units Default Value Special Values fails, retain the connection 07/22/04 Opsol Integrators Inc.
OmniMessaging Functional Description 13 Billing Module (To purchase this additional module please contact your HP Sales Representative) OmniMessaging provides users a Billing module that can be used to generate files in customized CDR formats. The files can be made available to other modules that run on platforms, like HP-Unix, Alphaservers, etc. The OmniMessaging modules log every activity of the user and make the necessary information available to the Billing application.
OmniMessaging Functional Description 14 Virus Scan Module (To purchase this additional module please contact your HP Sales Representative) OmniMessaging performs the following: Filter out unwanted message. 1. Scan messages for rules. 2. Scan messages for virus. Rules: System / Domain /User level rules are defined in database. Rules can be applied to part of message like “Header” “Body” etc.
OmniMessaging Functional Description 15 Parental Control and Content Router (To purchase this additional module please contact your HP Sales Representative) OmniMessaging performs the following: Filter out unwanted message. 3. Scan messages for rules. 4. Scan messages for virus. Rules: System / Domain /User level rules are defined in database. Rules can be applied to part of message like “Header” “Body” etc.
OmniMessaging Functional Description 16 ACH / EDI Support with Digital Signatures X.509 (To purchase this additional module please contact your HP Sales Representative) 16.1 Secure email is defined as 1) The value-bearing portion, or the entire body, must be encrypted. 2) The value-bearing portion, or the entire body, must be authenticated via digital certificate. 16.2 Some requirements for Secure email 1) Customers want to be able to send us financial transactions using secure email.
OmniMessaging Functional Description Netscape. A user may optionally choose to encrypt or digitally sign the message or even a combination of encryption and signature. The message is then delivered via the internet to Bank’s mail server. The OmniMessaging POP client retrieves these messages from the remote (Lotus, Exchange, Hotmail etc) Mail server and securely stores these messages in the OmniMessaging Message Store. The business application requests for new messages via a published interface.
OmniMessaging Functional Description 17 Deliver Invoices, Statements via email (To purchase this additional module please contact your HP Sales Representative) The ZLEMail Adapter is provided to email enable applications. Applications can send email messages to internet users via the ZLE Adapter. The Adaptor can be invoked by applications on the platform as well as applications off the platform. The adaptor supports a simple input buffer.
OmniMessaging Functional Description 18 Consolidates users email addresses (To purchase this additional module please contact your HP Sales Representative) The POP Client is an email gathering utility to retrieve mails from a mailbox residing on a remote system using POP3 protocol to a local OmniMessaging mailbox on our system. The POP client is an add-on component to the OmniMessaging Core. The POP Client interfaces with the users email server using the POP3 protocol and retrieves the mails for the user.
OmniMessaging Functional Description 19 Voice Mail server (To purchase this additional module please contact your HP Sales Representative) OmniMessaging Voice Mail server is for Carriers and Mobile Operators supporting millions of voice mail boxes. Voice messages can be accessed via standard phones, mobile phones, email and MMS clients. The solution is completely integrated with the carriers Network Protocols to provide Intelligent Messaging Services.
OmniMessaging Functional Description 19.3 Deleting Voice messages The system deletes the voice messages from the message store in a two phased approach. The messages are first marked for logical deletion and control returned immediately to the user. The task of physical deletion is performed later in deferred online mode. 07/22/04 Opsol Integrators Inc.
OmniMessaging Functional Description 20 OmniIVR Solution Overview (To purchase this additional module please contact your HP Sales Representative) The OmniIVR packaged solution consists of the Omni Software and the HP Open Call Platform. The OmniIVR solution is superior because of its large scalability and tight enterprise integration with the United States House of Representatives, “The Telco”, business applications. 21 Solution details 21.
OmniMessaging Functional Description The prompts are delivered to the central Tandem system and then propagated to all the HP Open Call servers in real time. The update is almost instantaneous and with this method the operator does not need to worry about inconsistency between the servers. Custom messages can be recorded using standard phones. 21.3 Adding dynamic content to the prompt The prompts can be sequenced to create the flow of static as well as dynamic data.
OmniMessaging Functional Description A logging facility is provided by the OmniIVR application. It identifies the status of each call, duration, success / failure etc. Detailed CDRs are logged so that they can be used for billing and audit purposes. 21.7 Scaling for volumes OmniIVR has been designed for the enterprise so that all components can be replicated to handle large volumes. This allows configuring multiple Call Control and multiple Call Processing instances.
OmniMessaging Functional Description OmniIVR Tandem Call Processing Module 22.1 OmniIVR Call Processing module This module is deployed on the Tandem server and provides the guts of the call processing. It communicates with the OmniIVR Call Control module to get the data from the caller. The data is transformed and passed to the Stand-In processes.
OmniMessaging Functional Description 22.3 Call Flow programming Call Flow programming is performed with an easy to use Web based Service Creation Tool. 22.4 Reports and Statistics for IVR servers The Console is a Web based interface to administer, configure and manage the OmniIVR solution. Customer will have modification rights to change the look and feel of the front end html screens.
OmniMessaging Functional Description Stats table structure Reports are generated from stats table, which stores the statistics for CP, CTI and CC. Structure of stats table is show below.
OmniMessaging Functional Description Options for Reports Report generation is partially automated with the help of generation logic provided in Report Generation screen. In case of reports, which are timely based, the type of report generated is based on the difference between end time and start time. The table shows the difference in the start time and time and the type of report generated.
OmniMessaging Functional Description Agent Statistics and Reports Agent statistics for all the agents can be generated. Input Start_date, End_date, Start_time, End_time Output Agent Statistics Report Constraints Output Attributes Agent Id Total Calls Average Call Time Maximum call Time Minimum Call Time 07/22/04 Opsol Integrators Inc.
OmniMessaging Functional Description Agent Statistics for particular Agent Agent Statistics for a particular Agent can be generated. Input Start_date, End_date, Start_time, End_time, Agent_Id Output Agent Statistics Report Constraints Output Attributes Total Calls Average Call Time Maximum call Time Minimum Call Time 07/22/04 Opsol Integrators Inc.
OmniMessaging Functional Description Emailing and downloading options for reports Reports can be downloaded in the form of CSV files or can be emailed to the users. Email 07/22/04 Opsol Integrators Inc.
OmniMessaging Functional Description Reports downloaded in Excel format 23 Additional features to increase revenue 23.1 Delivering confirmations, notifications via voice messages, email, fax 07/22/04 Opsol Integrators Inc.
OmniMessaging Functional Description The OmniMessaging components support message delivery to numerous touch points. With the OmniMessaging solution we can deliver statements, invoices, notifications to multiple touch points. Voice messages can be delivered to the card holder’s cell phone or the card issuing company’s phone. These messages can be application generated to notify of outstanding balances, payment receipt etc and may also include emails. 23.
