f3316e30d6
This API is a bit unfortunate as the caller will also
access the endpoint directly. E.g. like this:
output = bsc_mgcp_rewrite(...,
mgcp_net_src_addr(endp),
endp->net_end.local_port, -1,
In terms of "terminology" the "net" was meant to be bad
internet and the "bts" is the local and trusted network
segment. With this terminology the "bts" would be the
call-agent/MGW and "net" where the BSCs will send data
to but that is not the case and terminology actuallys
refers to:
* net: The addresses exposed to the entity that
made the MGCP call
* bts: The system where we get our data for the
local audio flow.
Fix the method but leave the API as it is. Use the net_end
in the net_src method and the bts_end in the bts_src method.
|
||
|---|---|---|
| .. | ||
| contrib | ||
| doc | ||
| include | ||
| src | ||
| tests | ||
| tools | ||
| .gitignore | ||
| AUTHORS | ||
| COPYING | ||
| Makefile.am | ||
| README | ||
| configure.ac | ||
| git-version-gen | ||
| openbsc.pc.in | ||
| osmoappdesc.py | ||
README
About OpenBSC ============= OpenBSC is a minimalistic implementation of the GSM Network, with particular emphasis on the functionality typically provided by the BSC, MSC, HLR, VLR and SMSC. Its currently supported interfaces towards the BTS are: * Classic A-bis over E1 using a mISDN based E1 interface. In other words, you can connect existing GSM Base Transceiver Station (BTS) through E1 to OpenBSC. So far, we have only tested the Siemens BS-11 Test reports with other BTS are much appreciated! * A-bis over IP as used by the ip.access nanoBTS product family You can find the project documentation at http://openbsc.gnumonks.org/ This project is still in its early days, and there are lots of areas where it doesn't behave as per GSM spec. Harald Welte <laforge@gnumonks.org> libosmocore =========== Please note that as of March 2010, OpenBSC has a dependency to a library called "libosmocore". You can obtain that library from git://git.osmocom.org/libosmocore.git