Hi Rene,
Actually it is sending the validity_period, here is an example,
addresses and data suppressed:
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: SMPP PDU 0xb312fe0 dump:
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: type_name: submit_sm
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: command_id: 4 = 000000x4
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: command_status: 0 = 000000x0
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: sequence_number: 3254 =
0000xcb6
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: service_type: NULL
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: source_addr_ton: 2 =
000000x2
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: source_addr_npi: 1 =
000000x1
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: source_addr: "******"
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: dest_addr_ton: 2 = 000000x2
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: dest_addr_npi: 1 = 000000x1
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: destination_addr: "********"
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: esm_class: 0 = 000000x0
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: protocol_id: 0 = 000000x0
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: priority_flag: 0 = 000000x0
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: schedule_delivery_time: NULL
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: validity_period:
"000000000500000R"
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: registered_delivery: 1 =
000000x1
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: replace_if_present_flag: 0
= 000000x0
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: data_coding: 0 = 000000x0
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: sm_default_msg_id: 0 =
000000x0
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: sm_length: 135 = 00000x87
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: short_message:
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: Octet string at 0xb0bca20:
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: len: 135
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: size: 136
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: immutable: 0
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: data: .....
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: Octet string dump ends.
2013-06-29 16:06:58.063 [22471] [2030] DEBUG: SMPP PDU dump ends.
After this, and note that I receive all MT requests with a SMSC HTTP of
system-type kannel, I receive an HTTP GET to the URL (any sensible data
suppressed):
http://localhost:30010/smppsmsc?username=*****&password=*****&to=*****&text=******&from=*****&coding=0&charset=UTF-8&account=******&smsc=smppsmsc&dlr-url=http%3A%2F%2Flocalhost%3A8177%2F%3Fusername%3D******%26password%3D******%26dlr-url%3D3932d084-f373-4034-b8bc-8249f8befe73%26dlr-mask%3D%25d%26dlr-mid%3D3932d084-f373-4034-b8bc-8249f8befe73&dlr-mask=3
Where I do not see any validity being passed, so I wander if the problem
is with the communication between smppbox and bearerbox, of the
bearerbox and the http request or the configuration.
The configuration I have for the HTTP SMSC is (any sensible data
suppressed):
group = smsc
smsc = http
smsc-id = smppsmsc
smsc-username = *******
smsc-password = ******
system-type = kannel
send-url = http://*****:*****/*****
port = ****
connect-allow-ip = "******"
no-sender = false
no-coding = false
no-sep = true
allowed-smsc-id = smppsmsc
reroute-dlr = true
dlr-url = http://****:****/?username=*****&password=*****
Everything works, MT, MO and DLR, but I don't receive the validity
period given by the ESME :-(
Best regards,
Paulo Correia
Em 29-06-2013 14:02, Rene Kluwen escreveu:
Probably your ESME is not sending a (valid) validity period.
*From:*users [mailto:[email protected]] *On Behalf Of *Paulo
Correia
*Sent:* zaterdag 22 juni 2013 11:26
*To:* [email protected]
*Subject:* Re: SMPPBox and the validity period when submiting short
message
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
