Thank you Malthe,
I can't change the SMS aggregator's server settings, so if they don't
use HTTPS then also the smsc-module of Kannel must also use HTTP.
I couldn't find post-url or get-url for smsc-group, only send-url.
Maybe I didn't explain the requirement clear enough: I don't mean sms-
service but smsc.
Attached the settings:
# #################
# SMSC HTTP #
# #################
#
group = smsc
smsc = http
smsc-id = HTTP
system-type = generic
smsc-username = test
smsc-password = test
port = 14000
log-file = /tmp/smsc-http.log
log-level = 0
send-url = "http://192.168.1.5/test/sms.php?from=%P&to=%p&text=%b";
status-success-regex = "ok"
status-permfail-regex = "failure"
status-tempfail-regex = "retry later"
allowed-smsc-id = HTTP
In my local network I have this sms.php, that receives both GET and
POST requests, and logs them so I can see, if the request coming from
Kannel is POST or GET.
I would need that when I send an MT through Kannel, it would
communicate with this "send-url" -script with POST-method. And vice
versa: MO reception would also need to be in POST. According to
documentation the reception is limited to the same syntax/format as
smsbox-reception, so it wouldn't be customizable.
But I have seen few posts / web pages where people had claimed that
POST method is possible.
Best regards,
Antti
On 17.4.2010, at 9.14, Malthe Borch wrote:
On 17 April 2010 00:38, Antti Karvonen <lis...@karvonen.info> wrote:
But I still wonder if there was some undocumented way to configure
the HTTP
interface of Kannel so that it would communicate via POST instead
of GET.
Use ``post-url`` instead of ``get-url``.
That said, what's driving you to require POST? There's no difference
on a protocol level––it's just semantics.
To secure your installation, use HTTPS.
\malthe
