aboutsummaryrefslogtreecommitdiffstats
path: root/openbsc/include/openbsc/rtp_proxy.h
diff options
context:
space:
mode:
authorAndreas Eversberg <jolly@eversberg.eu>2012-01-16 09:29:28 +0100
committerAndreas Eversberg <jolly@eversberg.eu>2015-12-27 20:00:40 +0100
commit990b41308770426eec50cbee6ac5f270f93afee2 (patch)
tree74721fb3daae417805c32a04a00a43dcc993b9f3 /openbsc/include/openbsc/rtp_proxy.h
parentcdc548cb0ac79a6eef3903872cc6e73eaf6f59ae (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.
Diffstat (limited to 'openbsc/include/openbsc/rtp_proxy.h')
-rw-r--r--openbsc/include/openbsc/rtp_proxy.h5
1 files changed, 3 insertions, 2 deletions
diff --git a/openbsc/include/openbsc/rtp_proxy.h b/openbsc/include/openbsc/rtp_proxy.h
index 52ffefd27..a5f6a2bea 100644
--- a/openbsc/include/openbsc/rtp_proxy.h
+++ b/openbsc/include/openbsc/rtp_proxy.h
@@ -40,8 +40,9 @@
enum rtp_rx_action {
RTP_NONE,
- RTP_PROXY,
- RTP_RECV_UPSTREAM,
+ RTP_PROXY, /* forward from BTS to BTS */
+ RTP_RECV_UPSTREAM, /* forward to application */
+ RTP_RECV_APP, /* receive RTP frames from application */
};
enum rtp_tx_action {