Hi again,
Just wondering, no one has ad any issues receiving the SMS validity from
an ESME on smppbox or opensmppbox and then sending it through the HTTP
SMSC of type kannel?
I have the following configuration:
ESME <---(smpp)---> SMPPBOX <---(socket internal)---> BEARERBOX
<---(HTTP using HTTP SMSC kannel)---> MyApp
And when a ESME sends an sm_submit with validity the URL called to MyApp
does not show that validity, as it should from the smsc_http.c source.
If smppbox and opensmppbox have something in common, both should suffer
from the same issue.
I was hopping there was someone else with the same issue and a solution.
Best regards,
Paulo Correia
Em 13-06-2013 22:51, Paulo Correia escreveu:
Hi,
Just adding some info, when looking at the smsc_http.c of kannel 1.5
(the one in use) I see, on the kannel_send_sms function (the one used
for system-type=kannel):
...
if (sms->sms.validity != SMS_PARAM_UNDEFINED)
octstr_format_append(url, "&validity=%ld", (sms->sms.validity
- time(NULL)) / 60);
if (sms->sms.deferred != SMS_PARAM_UNDEFINED)
octstr_format_append(url, "&deferred=%ld", (sms->sms.deferred
- time(NULL)) / 60);
...
So, can it be a limitation on the smppbox routing to the http smsc? Or
am I missing something?
Best regards,
Paulo Correia
Em 13-06-2013 16:47, Paulo Correia escreveu:
Hi,
We've been using smppbox in the last two years and routing messages
to an HTTP SMSC, with the following configs:
* SMPPBOX:
group = smppbox
admin-port = XXXXX
admin-password = XXXX
status-password = XXXX
bearerbox-host = "localhost"
bearerbox-dcs = utf-8
smppbox-port = XXXX
system-id = "skysmssmpp"
log-file = "/home/smsuser/logs/smppbox_smppbox.log"
log-level = 0
access-log = "/home/smsuser/logs/smppbox_smpp_access.log"
store-type = spool
store-location = "/home/smsuser/data/spool/smppbox"
transparent-mo-routing = yes
transparent-mo-routing-account = yes
time-to-keep-status = 604800
* SMSC:
group = smsc
smsc = http
smsc-id = smppsmsc
smsc-username = xxxxxxxxxxx
smsc-password = xxxxxxxxxxx
system-type = kannel
send-url = http://localhost:zzzzz/smppsmsc
port = yyyy
connect-allow-ip = "127.0.0.1;..."
no-sender = false
no-coding = false
no-sep = true
allowed-smsc-id = smppsmsc
reroute-dlr = true
dlr-url =
http://localhost:yyyy/?username=xxxxxxxxxxxxxxx&password=xxxxxxxxxxxxxxx
We do get all submit_sm from the ESMEs and deliver all MOs and DLRs,
but if an ESME sends a submit_sm with a validity_period, we do not
see it reflected on the URL http://localhost:zzzzz/smppsmsc ...
Does anyone have the same problem, even in OpenSMPPBox?
Best regards,
Paulo Correia
