From 06f4fc79a221b2451bdbf9e1035d42f3bf9eaf1c Mon Sep 17 00:00:00 2001 From: Holger Hans Peter Freyther Date: Tue, 29 Mar 2011 17:46:14 +0200 Subject: bsc: Make the MSC node a child of CONFIG_NODE The VTY code calls the write function for nodes in the order of registration of the node and not in terms of hierachy of nodes. This means that the e1_input code is written before the MSC node that was the child of the network. Make the MSC_NODE a direct descendant of the CONFIG_NODE and avoid this issue. --- openbsc/src/libcommon/common_vty.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'openbsc/src/libcommon') diff --git a/openbsc/src/libcommon/common_vty.c b/openbsc/src/libcommon/common_vty.c index e974f2d88..f14dbca2d 100644 --- a/openbsc/src/libcommon/common_vty.c +++ b/openbsc/src/libcommon/common_vty.c @@ -84,7 +84,7 @@ enum node_type bsc_vty_go_parent(struct vty *vty) } break; case MSC_NODE: - vty->node = GSMNET_NODE; + vty->node = CONFIG_NODE; break; case TRUNK_NODE: vty->node = MGCP_NODE; @@ -155,7 +155,7 @@ gDEFUN(ournode_exit, vty->index = NULL; break; case MSC_NODE: - vty->node = GSMNET_NODE; + vty->node = CONFIG_NODE; break; case TRUNK_NODE: vty->node = MGCP_NODE; -- cgit v1.2.3