1. Interact
Messaging Gateway
April 2010

2. Introduction
The Mobile Messaging Gateway is a turn key solution to enable
operators to provide third party application developers with a quick,
standard, and easy way to interface with their messaging platforms
(i.e.: SMSC & MMSC).
It offers:
 MMS sending and reception.
 SMS sending and reception.
 WAP Push sending (Service Indication).
 SMS/MMS delivery report reception.
2 Messaging Gateway 15/04/2010

3. With Mobile Messaging Gateway, you can add mobile features to
your existing intranet, extranet or Internet solutions and rapidly
develop and deploy new MMS/SMS/push-enabled applications.
3 Messaging Gateway 15/04/2010

4. Our Value Proposition
 Linux based Platform ensuring:
 Compliance with the industry standards.
 Quick time-to-market and start the revenue stream
 High availability and minimal response times of the platform
 Easy provisioning of messaging services
 Centralized management
 Integrated reporting tool
4 Messaging Gateway 15/04/2010

5. Features
 System logging and tracing for all the different components of the
platform enabling the operator to trace and troubleshoot the
problem and determining the cause of failure.
 Easy monitoring and alarm generation to be used with any network
management system.
 Scalable and can be used in a cluster.
 Supports all types of messages: text, monophonic Ring tones,
logos, picture messages, WAP push, Flash SMS, &MMS.
5 Messaging Gateway 15/04/2010

6. Features
 Simple HTTP interface / SOAP WEB Service for integration with
third party applications.
 Comes with an easy to use web admin interface to manage the
different developer accounts and operator connections.
 Supports SMPP and UCP protocols for sending and receiving
SMSs.
 Supports MM7 & EAIF standards to interface with the MMSC.
 Full delivery reports support for both SMS and MMS.
6 Messaging Gateway 15/04/2010

7. Architecture
 Routing Engine: to MT messages
based on the receiver number prefix,
and to route MO messages based on
the received short code, Connection
ID and Keywords.
 Queuing engine: to manage
messages priority and queuing (FIFO).
 Messaging engine: to handle
converting HTTP API parameters to
compliant SMSC/MMSC protocols.
7 Messaging Gateway 15/04/2010

8. Architecture
 DLR engine to receive DLRs from SMSC/MMSC and route them
Applications
 Reporting Engine: A web reporting tool to displays CDRs for custom
periods of time.
8 Messaging Gateway 15/04/2010

9. Architecture
9 Messaging Gateway 15/04/2010

10. Technology
 The platform is developed using the industry proven tools to ensure
carrier grade performance and high availability.
 Being very stable and easy to administrate, Linux became one of the
most desirable operating system to be used in carrier grade applications.
 MySQLRDBMS is used as a high performance, cost effective RDBMS
suitable for carrier grade applications handling large scale databases.
10 Messaging Gateway 15/04/2010

11.  HP Proliant rack mounted servers are recommended for full
redundancy and RAID options to ensure high availability and
performance of the platform.
 The entire solution and integration is based on Java technology
running on Tomcat 6 application servers. This ensures highest
performance and scalability.
11 Messaging Gateway 15/04/2010

12. Interact Egypt
7B Omar Shaaban,
Thank you! Nasr city, Cairo
http://Egypt.interact.it
12 15/04/2010