while doing the patch to make this work, i found out that all things are
in place except a way to configure bearerbox to route to source boxes
and line that would add boxc_id to dlrs. as i have no idea what would be
the best way to make it configurable, i just did simple patch that
hardcodes the source routing by putting source box_id into dlrs. it is
good enough for me at this moment but having it configurable would be
definitely better. if some core dev would tell me what configuration
option should be introduced and it would be easy to implement (i forgot
a lot about c coding, last time coded in c around 10 yrs back), i could
enhance the patch.
i tested the patch with two sqlboxes, bearerbox and fakesmsc. sending
messages from each sqlbox resulted in getting dlrs to the sqlbox which
originated the message so at least for this scenario it seems to work.
miroslav
Dne 6.12.2010 11:44, Miroslav Šulc napsal(a):
> hello,
>
> is it possible to route dlrs always to the box where the original
> message came from? i would like to run bearerbox with two sqlboxes, each
> running over different database. and to update status of the messages in
> the databases, i need to receive the dlrs at the same database from
> which the original message came. i read the documentation several times
> and googled too, but i did not find how to do this.
>
> thanks for any help.
>
> miroslav
>
>
# HG changeset patch
# Parent e7538ab91f8ceecfdfbefa495321127e85b4238f
diff --git a/gw/bb_boxc.c b/gw/bb_boxc.c
--- a/gw/bb_boxc.c
+++ b/gw/bb_boxc.c
@@ -307,6 +307,7 @@
debug("bb.boxc", 0, "boxc_receiver: sms received");
/* deliver message to queue */
+ msg->sms.boxc_id = octstr_duplicate(conn->boxc_id);
deliver_sms_to_queue(msg, conn);
if (conn->routable == 0) {
