Enterprise Messaging Gateway - TAP Interface Manual
Enterprise Messaging Gateway TAP Interface Manual
Confidential
Version: 1.2.4
Version Control Information:
Version
Date
Author
Changes
1.1
1.2
1.2.4
14 - Jan - 2009
11 - Jul - 2013
05 – Aug – 2013
Mikhail Grinfeld
Andy Klassman
Amit Rahat
First draft
Update Sprint details
Update Access Number
P A GE 1 OF 5
Enterprise Messaging Gateway - TAP Interface Manual
Table of Contents
1.
INTRODUCTION ................................................................................................................................ 3
A.
B.
C.
D.
2.
PURPOSE ........................................................................................................................................ 3
OBJECTIVE OF THIS DOCUMENT .................................................................................................... 3
GLOSSARY ...................................................................................................................................... 4
REFERENCES.................................................................................................................................. 4
CONNECTING TO THE SERVICE .................................................................................................. 5
A.
1)
2)
BASIC CONNECTIVITY PARAMETERS.............................................................................................. 5
Access Details ................................................................................................................................. 5
Supported Connection Details ........................................................................................................ 5
P A GE 2 OF 5
Enterprise Messaging Gateway - TAP Interface Manual
1. Introduction
A. Purpose
The attached document should help understand the needs and method to
deliver wireless messages through the Sprint EMG TAP interface. The TAP
server allows clients to deliver one-way SMS messages to appropriate
receiving devices via dial up modem.
This document assumes a level of familiarity with TAP functionality, and
follows the protocol specification Version 1.8
For further assistance please contact your sales/project manager.
B. Objective of this Document
This document is meant to outline the technical connectivity requirements for
sending wireless messages from the service provider/mobile operator to the
Sprint system. This connectivity is used for receiving wireless messages from
the network to the Sprint system. Sprint will be the Server (Receiver) side and
act as carrier gateway, while the client can be a transient client
The connection settings explained here are based on connectivity using the
TAP protocol.
Please note that connectivity using other protocols is possible as well - for
further assistance please contact your sales/project manager.
P A GE 3 OF 5
Enterprise Messaging Gateway - TAP Interface Manual
C. Glossary
Name
Value
TAP
Telelocator Alphanumeric Protocol
Modem
Dial-up modem capable of sending TAP messages
Access Number
Dial up phone number modem calls to send message
Pager ID
Phone Number of Receiver Mobile Device
SMS
Short Message received to mobile device containing
the alphanumeric message text
D. References
Document Name
Version
TELOCATOR ALPHANUMERIC PROTOCOL
Version 1.8
Link
TAP_V1P8.pdf
P A GE 4 OF 5
Enterprise Messaging Gateway - TAP Interface Manual
2. Connecting to the Service
A. Basic Connectivity Parameters
1) Access Details
Sprint will be the Server (Receiver) side and act as carrier gateway. The client
should call the number to send his messages to the following addresses:
Item
Type
Access Number
Production Receiver 1
1-888-656-1727 (toll-free) or 1-973-859-7932
2) Supported Connection Details
Baud Rate:
1200 / 2400
Data Bits:
7
Parity:
Even
Stop Bits:
1
Modulation:
Bell Standard (103,212A), CCITT V.21, V.22, V.22bis
Error Correction:
Disabled
Data Compression:
Disabled
P A GE 5 OF 5