TeleMessage Multi-Alert enables
you to:
Send,
receive, reply to and forward messages (voice, music, text,
image, document) to and from all
existing communications media (mobile
or landline phone, SMS, fax, e-mail Instant Messengers and
pagers.)
No
worrying about standards, formats and protocols, networks.
Below is a list of steps used to send and trace a
message.
(1) External system sends
message to be delivered using TeleMessage Multi-Alert XML
(2) TeleMessage receives
message and reports MessageID and MessageKey for future status and reply
queries
(3) TeleMessage messaging
center sends message to devices and collects replies
(4) External system queries
TeleMessage for status and replies
(5) TeleMessage reports
replies & delivery status back to external system
Click to enlarge (new window)
As explained TeleMessage’s Multi-Alert Service
acts as a seamless layer which is built of three tiers:
|
Access and Input tier
The Access and Input tier provides 'log on' entrance into the system. Integration with third party systems - be it partial or complete - is done through interfaces defined in this tier (POP3, IMAP4, SMTP, SMPP, SMS, MMS or XML / HTTP-Post for application level integration). All servers are fully monitored and load balanced.
|
|
Management and Storage tier
The Management and Storage tier is the heart and brains of the system. It includes the database (Oracle for example) & storage vault (EMC2 for example) where all messages going through the system are locked away, message queue management and deployment, 24x7 monitoring services (Supported SNMP traps), maintenance & administration functions and finally, the billing engine. The whole tier is carefully shielded and well protected (Checkpoint Firewall and Cylink VPN shield , for example).
|
|
Delivery tier
The Delivery tier ensures that all messages leaving the system are passed by the Message Management Server(s) to the applicable Dispatcher(s) for fail safe delivery. Each Dispatcher is responsible for transforming the generic multimedia message to the specific format of the recipient device, delivering the message, handling local resend and retry logic, and reporting the exact status of delivery back to the database for the user to view.
|
Messages to be sent are placed in the databases' message queue, which are continuously polled by the Message Management servers. Next, the Message Management servers ask the Service Broker for the best available dispatcher. The broker is designed to find the "best": taking into account server type, CPU power, availability, least cost routing, load balance and bandwidth statistics. The message is then handed to the Dispatcher and the Message Management server is free to pull the next message from the queue. The Dispatcher is responsible for the translation of the generic message into the format required by the specific delivery device, and for the successful delivery of the message.
Learn more by viewing our XML
explanation presentation and
API documents.
|
