aboutsummaryrefslogtreecommitdiffstats
path: root/openbsc/src/utils
diff options
context:
space:
mode:
authorAndreas Eversberg <jolly@eversberg.eu>2012-01-16 09:29:28 +0100
committerIvan Kluchnikov <kluchnikovi@gmail.com>2015-05-26 15:55:12 +0300
commitbc1aaacf7412e7a042e28be75139a72de3324c93 (patch)
tree5fad78b6169cf2f0efaf9786429f6f6df17d861d /openbsc/src/utils
parent4c8e8f990a24fc5ecb24c5c21c944d8ab4dc7c1e (diff)
Add traffic forwarding via RTP to remote application
Instead of forwarding traffic through MNCC interface, traffic can be forwarded to a given RTP peer directly. A special MNCC message is used to control the peer's destination. The traffic can still be forwarded through MNCC interface when this special MNCC message is not used. It also works with E1 based BTSs. In conjunction with LCR's "rtp-bridge" feature, the RTP traffic can be directly exchanged with a remote SIP endpoint, so that the traffic is not forwarded by LCR itself. This way the performance of handling traffic only depends on OpenBSC and the remote SIP endpoint. Also the traffic is exchanged with the SIP endpoint without transcoding, to have maximum performance. Increment MNCC version to 5. Conflicts: openbsc/tests/gbproxy/gbproxy_test.c
Diffstat (limited to 'openbsc/src/utils')
-rw-r--r--openbsc/src/utils/bs11_config.c6
1 files changed, 6 insertions, 0 deletions
diff --git a/openbsc/src/utils/bs11_config.c b/openbsc/src/utils/bs11_config.c
index e8acb461a..f459744aa 100644
--- a/openbsc/src/utils/bs11_config.c
+++ b/openbsc/src/utils/bs11_config.c
@@ -83,6 +83,12 @@ struct osmo_counter *osmo_counter_alloc(const char *name)
return NULL;
}
+/* dummy function to keep rtp_proxy.c happy */
+int tch_frame_down(struct gsm_network *net, uint32_t callref, struct gsm_data_frame *data)
+{
+ return 0;
+}
+
int handle_serial_msg(struct msgb *rx_msg);
/* create all objects for an initial configuration */