diff options
author | Andreas Eversberg <jolly@eversberg.eu> | 2012-01-16 09:29:28 +0100 |
---|---|---|
committer | Ivan Kluchnikov <kluchnikovi@gmail.com> | 2014-05-06 17:21:24 +0400 |
commit | 166b32b8d696981955b7d6bb0ec7ac1b801fff47 (patch) | |
tree | f3f2fab54a8cecd44cf5cb1023b83b9058f44f66 /openbsc/contrib | |
parent | f2f94ce900bae621dca89571bc526fef4a71489c (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/contrib')
0 files changed, 0 insertions, 0 deletions