Hi all,

We've figured out why we're not getting the command_status to our DLR, so I
thought I would post this in case anyone else had a similar problem.

We're not receiving the command_status to our DLR because we're sending a
concatenated message. Relevant code is from bb_smscconn.c:

void bb_smscconn_send_failed(SMSCConn *conn, Msg *sms, int reason, Octstr
*reply)
{
    if (sms->sms.split_parts != NULL) {
        handle_split(conn, sms, reason);
        octstr_destroy(reply);
        return;
    }
    ...

Presumably this is because each SMS part can have its own command_status,
and Kannel isn't set up to pass multiple command_status' to a DLR.

It would be nice to be able to access all command_status' for a
concatenated message (or at least the first), but we can also work around
this.



----------Original message----------
From: S G <[email protected]>
To: [email protected]
Cc:
Date: Wed, 15 Feb 2012 21:50:17 -0500
Subject: Passing command_status to DLR
Hello all,

Firstly, I want to to thank the devs for the awesome work they've put into
kannel--it has worked extremely well so far!

However, I've been scouring the kannel lists and user docs for details
about how to pass command_status to a dlr-url in Kannel 1.5.0, but alas I
have been unable to figure out how to do it (or even definitively figure
out if it is possible with kannel out of the box).  I have dlr-url and
dlr-mask working fine, but am unable to ever receive command_status to my
dlr script.

Our need for command status is similar to what I've seen others post about
on the list:  one of our carrier partners uses the command_status to return
different kinds of transactional error codes that our application needs
access to (including billing status).

Threads like this:

http://www.kannel.org/pipermail/users/2011-June/015893.html

state that the TLV meta data feature of 1.5.0 can be used to read the
command_status, but I am unable to find any examples of this in the mailing
list or in Appendix H of the User Guide--can someone give a kannel.conf and
corresponding dlr-url example that is successfully passing the
command_status?

Threads like these:

http://www.kannel.org/pipermail/users/2009-December/009427.html
http://www.kannel.org/pipermail/devel/2009-September/002926.html

suggest that this was patched into the "meta-data" functionality of Kannel
prior to 1.5.0 (and suggest that I shouldn't even need a TLV section to get
the dlr_status parameter?), however I have been unable to get anything to
show up in the %D parameter passed to my dlr-url.

I'm also not seeing the command_status passed via the %A or binfo
parameters (we're printing every % parameter passed to our DLR script), as
per these threads:

http://www.kannel.org/pipermail/users/2011-June/015926.html
http://www.mail-archive.com/[email protected]/msg14125.html

It's possible I have overlooked instructions for how to do this on the
devel list--can someone show me a working kannel.conf and dlr-url example
that return command_status for submitted SMSs?

Other than this feature, everything about our Kannel setup is working
great.  Please let me know if you need any addition info from me.

Thanks!

Reply via email to