SMPPSim and MO Messages

"Martin Woolley" <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <000401c1bf59$bdf06f10$667714ac@martin>
>From: [email protected] [mailto:[email protected]]
>On Behalf Of [email protected]
>Sent: 22 February 2002 19:29
>To: [email protected]
>Subject: SMPP Simulators?
>
>Hey guys,
>I need to do some SMPP testing simulations on Kannel CVS. What simulators
do
>you guys use? I used smppsim, and as far as I can tell, I can send an sms
to
>it, but do you guys know how to get it to send msgs to kannel?
>thanks =)

Hi,

a friend passed the above email requesting info about SMPPSim and mobile
originated messages to me. I am the author of SMPPsim and yes, you can send
an SMS from SMPPSim to Kannel. An extract from the user guide follows. Make
sure you are running the latest version (01.11 Build 004) btw.

MOBILE ORIGINATED MESSAGES
SMPPSim provides three different ways in which to generate DELIVER_SM
messages which are sent from SMPPSim to your application, thus simulating
the delivery of mobile originated messages. These are as follows:
1. The smppsim.html form and the HTTPController object
2. Loopback Service
3. Delivery Service
Before looking at each of these methods, however, you should read the
section which follows on "Receivers".
Receivers
An *active* Receiver is a connection between an application and SMPPSim
which has sent a valid BIND_RECEIVER message and not yet sent an UNBIND
message. When your application issues its BIND_RECEIVER message, it should
include a correctly formulated ADDRESS_RANGE attribute. This field takes the
form of a regular expression
<http://gnosis.cx/publish/programming/regular_expressions.html> and
determines the subset of MO messages that are delivered using this Receiver
connection. When seeking to deliver a message, SMPPSim matches the
destination address of hte message against the regular expression contained
within the ADDRESS_RANGE field of each active receiver. It chooses from
within candidate Receivers on a round robin basis.
Examples of regular expressions to use when binding:
^1 - Messages whose destination address starts with "1" are delivered to
this receiver
^2 - Messages whose destination address starts with "2" are delivered to
this receiver
[0-9] - Messages whose destination address contains any combination of
numeric characters are delivered to this Receiver.


The smppsim.html form

In the SMPPSim home directory you will find a directory called www/. This
directory contains two html pages, including smppsim.html. Open the file in
your web browser. It consists of a form which allows you to specify the
attributes of a DELIVER_SM message. Submitting the form send the message
attributes that you provided over HTTP to the SMPPSim HTTPController. There
it is decoded and turned into a DELIVER_SM message which is sent via one of
the active (bound to) Receiver objects to your application. Note that at
least one active Receiver object must be available for this feature to work.
Remember to follow the instructions on the smppsim.html form and modify the
host name or IP address specified and if necessary, the port, to suit your
installation:
<form name="form1" method="get" action="http://127.0.0.1:10099">

Loopback Service
The loopback service is enabled by setting the LOOPBACK property to TRUE in
the props file. When activated in this way and provided there is an active
Receiver object, all messages submitted to SMPPSim (SUBMIT_SM) via a
Transmitter object will be converted into corresponding DELIVER_SM messages
and returned via an active Receiver object. In other word, every message
your application sends gets delivered right back.
Delivery Service

SMPPSim includes a feature known as the Delivery Service. By setting the
DELIVERY_MESSAGES_PER_MINUTE property to a non-zero value, SMPPSim will
periodically send a DELIVER_SM message to your application. The specific
messages to send are set up in a comma separated variable (CSV) format text
file. The name of this file is specified in the SMPPSim properties file via
the DELIVER_MESSAGES_FILE property. Once again, as with all three of the
Mobile Originated Message features of SMPPSim, your application must bind as
a receiver at least once for there to be a path available to SMPPSim for the
delivery of such messages.


Martin Woolley
[email protected]
http://www.woolleynet.com/
http://www.mobilelandscape.co.uk/
http://www.j2medownload.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.