Hi Robert Not sure I get right your question.
I think you can craft your dlr-url and/or the script called by the dlr-url in order to, in addition to what you do now, pass that info to your partner. ie generate the dlr with the specific info you want to forward. For now your dlr-ulr is doing some magic to update the message status in your DB. So you can add to this script some extra magic to, in addition to what it does, do a call to the smsc box sending dlr info Hope this helps. Regards Alvaro |----------------------------------------------------------------------------------------| *7* Switch off as you go / Apaga lo que no usas / Débranchez au fur et à mesure. *q *Recycle always / Recicla siempre / Recyclez toujours P Print only if absolutely necessary / Imprime solo si es necesario / Imprimez seulement si nécessaire Le mar. 5 mai 2020 à 08:09, Robert Robinson <robert.robin...@textnow.com> a écrit : > Hello; > > > > We currently use Kannel 1.4.5 as a middleware box which sits between our > network and our partner network. We call into smsbox, using the HTTP API to > submit outbound messages to bearerbox, and using the sms-service to make > HTTP calls into our network when bearerbox submits messages to smsbox. We > interface with our partner using the smpp SMSC module. This works very well. > > > > Today, we can receive DLR reports for the outbound messages that we send > to our partner by adding the dlr-mask and dlr-url parameters to the HTTP > call we make to smbox. > > > > I would like to know how I can configure smsbox to allow for delivery > reports to be crafted for messages that sms-service delivers over HTTP. > Specifically, I am looking for a way to be able to signal back to our > partner specific SMPP deliver error codes when a message that is received > cannot be delivered. Is this possible with smsbox today? If so, what would > need to be included in the HTTP response returned on the call made by > sms-service? > > > > Thank you for any insight you can provide. > > ~Robert > > > > The sms-service config we use (callback host changed for sake of example): > > > > group = sms-service > > keyword-regex = .* > > catch-all = yes > > max-messages = 7 > > omit-empty = true > > alt-charset = "UTF-8" > > get-url = > http://sms.example.com/sms?to=%P&from=%p&message=%a&udh=%u&bin_message=%b > > concatenation = true > > accept-x-kannel-headers = true >
