RE: disabling incoming SMS

<[email protected]> Sun, 24 Feb 2019 21:50:51 +0100
Newsgroups gmane.comp.mobile.kannel.devel,gmane.comp.mobile.kannel.user
Message-ID <[email protected]>
I think disabling MO in the AT module is possible if you set sim =
buffering
to false and specify the proper CNMI string for your modem that disables =
MO
indications.

=3D+=3D Rene

-----Oorspronkelijk bericht-----
Van: users <[email protected]> Namens Stipe Tolj
Verzonden: zondag 24 februari 2019 21:06
Aan: [email protected]
CC: [email protected]
Onderwerp: Re: disabling incoming SMS

Am 19.02.19 17:46, schrieb Stuart Kendrick:
> I=92m seeing a lot of this in my logs:
>
> 2019-02-18T19:28:26.526495-08:00 vishnu smsbox[21580]: 2019-02-18
> 19:28:26 [21580] [5] INFO: Starting to service=20
> <#001#006'application/vnd.wap.mms-message> from <1111301000> to <1234>
>
> 2019-02-18T19:28:44.167763-08:00 vishnu smsbox[21580]: 2019-02-18
> 19:28:44 [21580] [5] INFO: Starting to service <11111301000 Error=20
> Invalid Number. Please re-send using a valid 10 digit mobile number or =

> valid short code. No service specified> from <+1121611611> to <1234>
>
> [=85]
>
> 2019-02-19T08:38:24.918834-08:00 vishnu smsbox[21580]: 2019-02-19
> 08:38:24 [21580] [5] INFO: Starting to service <11121611611 Error=20
> Invalid Number. Please re-send using a valid 10 digit mobile number or =

> valid short code. No service specified> from <+1121611611> to <1234>
>
> 2019-02-19T08:38:37.474384-08:00 vishnu smsbox[21580]: 2019-02-19
> 08:38:37 [21580] [5] INFO: Starting to service <11121611611 Error=20
> Invalid Number. Please re-send using a valid 10 digit mobile number or =

> valid short code. No service specified> from <+1121611611> to <1234>
>
> I speculate: someone has found my cellular modem number and is sending =

> me spam.
>
> For this application, I transmit SMS over the cellular modem; I =
don=92t=20
> want to receive anything.
>
>     * My carrier (AT&T) tells me that they cannot block in-bound SMS =
=96
>       they can enable bi-directional SMS or disable it: all or =
nothing.
>     * I disabled auto-answer on the modem =85 but this setting appears =
to
>       govern POTS, not SMS
>
>     * Is there a Kannel way (bearerbox or smsbox) to disable incoming
>       reception of SMS?
>     * Alternatively, is there a way to instruct Kannel to send =
requests
>       for Invalid Numbers (e.g. =911234=92) to /dev/null?
>     * Other ideas for dumping these messages? I=92m mostly annoyed by =
the
>       repetitive logging
>
> At the moment, I have a cronjob job which stops bearerox & smsbox,=20
> sleeps for several minutes (not clear to me why this is necessary),=20
> and then restarts them. This of course creates a dead zone, in terms=20
> of service, which is suboptimal.

Hi Stuart,

what you can do is to ensure that the "visible" impact is minimal. The =
SMSC
AT module has no way to "refuse" MOs directly. It will send any MO to =
your
connected smsbox instance.

If you have no application driven MOs that you want to receive, then you =
can
drop the MOs to nirvana and ensure that there is no response bounced =
back to
the originator, i.e. via config context

   group =3D sms-service
   keyword =3D default
   text =3D "No action specified"
   max-messages =3D 0

You WILL still see the MOs in the bearerbox access-log and the smsbox
access-log though.

It MAY BE an option to think about a config directive for the SMSC AT =
module
to "turn off" MO interpretation and simply drop anything we get on the
modem.

@devel: Anyone from the SMSC AT developer folks that wants to pick this =
up?


--
Best Regards,
Stipe Tolj

-------------------------------------------------------------------
D=FCsseldorf, NRW, Germany

Kannel Foundation                 tolj.org system architecture
http://www.kannel.org/            http://www.tolj.org/

[email protected]                  [email protected]
-------------------------------------------------------------------