Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
200 views

SMSC SMPP Server-Client

The document describes an SMSC system with an SMPP server and client that provides high throughput routing of SMS messages. It has features like dynamic routing to select alternative carriers if connections fail, a web interface for management, and reporting on message volume and costs. The system allows administrators to define routes between countries/carriers, carrier profiles with costs and prices, and rules for selecting provider carriers for customer carrier routes.

Uploaded by

Boban Pavloski Bobio
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
200 views

SMSC SMPP Server-Client

The document describes an SMSC system with an SMPP server and client that provides high throughput routing of SMS messages. It has features like dynamic routing to select alternative carriers if connections fail, a web interface for management, and reporting on message volume and costs. The system allows administrators to define routes between countries/carriers, carrier profiles with costs and prices, and rules for selecting provider carriers for customer carrier routes.

Uploaded by

Boban Pavloski Bobio
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8

SMSC Smpp Server/Client

Francesco Fiacchi
SMSC
Features:
SMSC with SMPP 3.4 Server and Client
High throughput (1,000/sec)
Dynamic Routing (for each route and for each Carrier sender
[Customer] can be chosen several Carrier providers in a position from
1 to 3: every SMS can go through the first provider, if problems arise
(the SMPP connection shuts down) the SMSC re-routes the messages
to the second provider and so on (Esme_ROK management).
Web Interface to manage Carriers, SMPP Connections Server/Client,
Routes and Cost/Price
NOC Interface: Status all Routes (active or not, SMS/sec) and Details
for each Route (Graphic, etc.)
Reporting: Messages Per Route, Message Per Carrier, Cost and
Revenues
Routes
Venezuela Movistar Routename
734-01 MMC
58414 Code
734-04
58424
First Form: SMSC Admin creates the Routes with following
data: Name of the Route (Routename), Country (drop
down menu with all countries), MMC (Mobile Code, with
+ sign allowing to add several MMCs in a row), Code
(mobile prefix, with + sign allowing to add several
Mobile Prefixes in a row
Venezuela Country
Carrier
Syniverse Carrier Name
Venezuela Movistar Routename 0.05
Technical Info
Cost 0.06 Price
CUSTOMER PROVIDER
Second Form: SMSC Admin creates the Carrier File with following data: Name of
the Carrier (Carrier Name), Routename (Several Routenames): for each Routename
a checkbox select if the Carrier is Provider or Customer or both: when checked
Provider admin inputs the cost the Carrier charges for that Route, when checked
Customer admin inputs the price that is charged to the Carrier for that Route.
Technical Info Open another form with administrative and technical info for that
Carrier (next slide)
Mexico Iusacell Routename 0.04 Cost 0.05 Price
Argentina Claro Routename 0.05 Cost 0.07 Price
Carrier Technical Info
Carrier
5680 Remote Port
9040 Local Port
sms.movistar.com.ve Remote URL/IP
Venezuela Movistar
TRX Connection Type (TRX, RX, TX)
xxx Password
xxx User
Routing
Venezuela Movistar Customer
Mexico IUSACELL Routename
Argentina CLARO Routename
Mexico
IUSACELL
Syniverse
Provider 1
0.05
0.03
Syniverse
RTX
Provider 2
0.05
0.03
0.05
0.03
Price
Fourth Form: SMSC Admin select the Customer (Carrier)
and for each Route (drop down menu) he/she selects the
Provider (Carrier) to pass the messages.
NOC
Controlling interface with Routenames, active or not and messages/sec
Routename Details

You might also like