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


Reply via email to