8 Nov
2009
8 Nov
'09
8:17 p.m.
Harald -
We have an SMS store and forward server for OpenBTS if you are
interested. It performs automatic redelivery attempts and "bounces"
undeliverable messages, but the interface is RFC-3428 and it is not
yet aware of TPDU types. (Bonus: It was written by John Gilmore.)
Some commercial SMSCs do support RFC-3428, though, so maybe this can
be made to fit into your model.
-- David
On Nov 7, 2009, at 9:30 PM, Harald Welte wrote:
Hi Bjoern,
On Sun, Nov 08, 2009 at 01:47:44AM +0100, Bjoern Heller wrote:
David A. Burgess
Kestrel Signal Processing, Inc.
I never used it much, but when I try to send an
SMS
from a MS to another one it is not delivered to the second MS.
OpenBSC displays that the SMS was received.
If I do a Location Update on the second Phone the SMS gets delivered.
Also if I enter the command "sms send pending".
yes, this is correct.
How can I setup automatic delivery?
this has not yet been implemented. I did not want to implement
that before
introducing some kind of SMS protocol and splitting the SMSC
functionality into
a separate process. But you are of course free to try to
implement it.
Attempting one delivery immediately after we receive the SMS is
probably a very
good idea.
But whether or not to regularly run timers to retry failed
deliveries, I am not
sure. With a long queue of pending messages like we had on HAR,
the load
iterating over that table can be very high, and it definitely will
cause
delays(latency) in processing of speech frames or even signalling.
Am I right, that OpenBSC first looks, if the
second subscriber is
connected
to the network and then delivers the message?
yes.
--
- Harald Welte <laforge(a)gnumonks.org> http://
laforge.gnumonks.org/
======================================================================
======
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300
175-7 Ch. A6)