From bc1aaacf7412e7a042e28be75139a72de3324c93 Mon Sep 17 00:00:00 2001 From: Andreas Eversberg Date: Mon, 16 Jan 2012 09:29:28 +0100 Subject: 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 --- openbsc/src/libbsc/bsc_api.c | 1 + 1 file changed, 1 insertion(+) (limited to 'openbsc/src/libbsc/bsc_api.c') diff --git a/openbsc/src/libbsc/bsc_api.c b/openbsc/src/libbsc/bsc_api.c index 76ceb2d8b..ee5aee349 100644 --- a/openbsc/src/libbsc/bsc_api.c +++ b/openbsc/src/libbsc/bsc_api.c @@ -31,6 +31,7 @@ #include #include #include +#include #include #include -- cgit v1.2.3