aboutsummaryrefslogtreecommitdiffstats
path: root/include/osmo-bts
diff options
context:
space:
mode:
authorHarald Welte <laforge@gnumonks.org>2014-08-18 19:14:58 +0200
committerHarald Welte <laforge@gnumonks.org>2014-08-24 17:29:16 +0200
commit54cbbb14503f3a99c13a882e67433b66c06235b9 (patch)
tree7f2f43f9c053e706ed4204b7451e53a857d21c69 /include/osmo-bts
parent3d836bcf3097d1fb09fd98eca10558b4fdb636c4 (diff)
Have osmo-bts request OML routes for all its MOs at startuplaforge/oml-router
During OML link start-up, osmo-bts now requests a OML route for each of the managed objects that it currently implements. This is done via the 'ORC' (OML Router Control) protocol, which is encapsulated in the extended IPA_PROTO_OSMO multiplex. The responses (ACK/NACK) are not yet processed inside osmo-bts.
Diffstat (limited to 'include/osmo-bts')
-rw-r--r--include/osmo-bts/oml_router_ctrl.h7
1 files changed, 7 insertions, 0 deletions
diff --git a/include/osmo-bts/oml_router_ctrl.h b/include/osmo-bts/oml_router_ctrl.h
index 7fe71dff..515e1e86 100644
--- a/include/osmo-bts/oml_router_ctrl.h
+++ b/include/osmo-bts/oml_router_ctrl.h
@@ -27,4 +27,11 @@ struct osmo_omlrctrl_register_req {
char name[0];
} __attribute__((packed));
+#include <osmocom/core/msgb.h>
+#include <osmo-bts/oml_routing.h>
+
+struct msgb *gen_orc_route_add(const struct oml_route *rt_in);
+struct msgb *gen_orc_route_del(const struct oml_route *rt_in);
+int abis_orc_sendmsg(struct msgb *msg);
+
#endif