Hi,
I will have to agree with Alvaro. Data mining, fraud, illegal and spam
messages are a can of worms that if kannel ever gets into, there is no way
out, with all legal ramifications. Not to mention a performance killer. Plus
a modular front end filtering would be much more flexible and customizable.
For the smppbox interface I would like to stress 2 things:
1) The average spammer or drug dealer won't use an SMPP connection to send
their messages. Upstream ESMEs will take responsibility for filtering them.
2) An intelligent firewall could be used, one that would block all offensive
packages, based on content.
BR,
Nikos
----- Original Message -----
From: <sreeka...@tngicube.co.in>
To: "Alvaro Cornejo" <cornejo.alv...@gmail.com>
Cc: <devel@kannel.org>
Sent: Thursday, November 19, 2009 2:41 AM
Subject: Re: Interface to bearerbox
Hello Alvaro,
Indeed the same would suffice for kannel, but when the it comes to usage
with smppbox, I personally don't think it is enough for that is our
experience.
Regards,
Sreekanth
Sent from BlackBerry® on Airtel
-----Original Message-----
From: Alvaro Cornejo <cornejo.alv...@gmail.com>
Date: Wed, 18 Nov 2009 18:55:44
To: Sreekanth GS<sreeka...@tngicube.co.in>
Cc: <devel@kannel.org>
Subject: Re: Interface to bearerbox
Hi
Kannel is a backend or a gateway for sending/receiving messages.
Kannel is designed to handle huge amount of SMS traffic transparently
to/from any external application, so you don΄t need to handle all kind
of protocol issues.
All you said is usually done through an external application of your
own, with whom you can do all filtering/billing/features you
need/want/desire.
You do not need to patch / modify kannel for do what you want. Just
with your own frontend will suffice.
Regards
Alvaro
On Wed, Nov 18, 2009 at 6:27 PM, Sreekanth GS <sreeka...@tngicube.co.in>
wrote:
Hello All,
We are presently engaged in using kannel as our SMPP Client, and for the
backend of smppbox. However, the interfacing to bearerboxes has been
quite
inadequate for us.
Hence, we plan to develop a viable interface to bearerbox that will/can:
1. Accept connections from smppbox, smsbox, sqlbox etc.
2. Log received MSG structs to a db pool.
3. Select specific messages from db pool using regex.
4. Transmit selected messages in (3) to bearerbox.
Similarly, catch MO/DLR returned by bearerbox.
1. Select specific messages from db MO/DLR pool using regex.
2. Send back the same to smppbox, smsbox, sqlbox etc.
Why all this?
smppbox transmits messages directly to bearerbox.
-> There is no hold and transmit scenario.
-> Manual approval of messages is not possible (in case of spam threats).
-> In between prioritizing of messages is not possible.
-> Manual modification of data is impossible, only automates is possible
using plugins.
-> Reject messages, hold messages (in case of queues at off-times/night)
for
a duration is impossible
-> There is no flexible control over the messages.
How to proceed:
1. Accept connections from other boxes.
2. Communicate with other boxes.
3. Store and retrieve data to and from db pool.
4. Communicate with bearerbox.
Hoping to see some helping hands,
Regards,
Sreekanth
--
|-----------------------------------------------------------------------------------------------------------------|
Envνe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perϊ, Mιxico y en mas de 180 paises. Use aplicaciones 2 vias via
SMS y GPRS online
Visitenos en www.perusms.NET www.smsglobal.com.mx y
www.pravcom.com
