I've read the document of the TRAI and I  can only shake my head....
That regulator has not understood at all how SMS works. Imagine Mr. Spammer wants to kill competition, the only thing he needs is to prefix tons of spam with XY- and everyone will blame XY-. Stupid excuse for the fact that operators are not good at finding out where an SMS came from. Furthermore its too easy to get around by sending SMS from outside India.

As others have said, Kannel has to stay neutral. This should, if, be done , done on application level. At maximum having a tool like a regexp function on application level which could be used for other things like replacing A with B or the like. Then it would be an universal feature. But doing it from the application sending the message is so darn simple that it becomes obsolete.



On 27.02.2009, at 19:10, Stipe Tolj wrote:

Stipe Tolj schrieb:
Hi list,

according to the TRAI, all SMSC in India need to use prefixes in TON=5
(alphanumeric) source addresses since 2009-02-01.

Please find a corresponding patch against 1.4.3 and CVS HEAD at

 http://www.kannel.org/~tolj/patchsets/TRAI/

along with the official direction statement of the TRAI.

I'm not sure if we want to "mainline" this into CVS, since it exposes another config directive to the smsc group. But as this is of general interest to all users from India, please feel free to incorporate the patch to your production
systems.

Any opinions if we want this (or modified) to go into CVS? I'm +0 on it, not
really sure and want to hear some opinions from the group.

thanks for the opinions. I'm fine with a negative vote to commit to CVS. I'm
also not comfortable with it as is.

Stipe

--
-------------------------------------------------------------------
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany

tolj.org system architecture      Kannel Software Foundation (KSF)
http://www.tolj.org/              http://www.kannel.org/

mailto:st_{at}_tolj.org           mailto:stolj_{at}_kannel.org
-------------------------------------------------------------------


Reply via email to