Oliver Smith
1d20ac48fc
Instead of having RAN/CN as parameter, make the function a bit simpler and only allow RAN. The motivation for this change is, that for MGW a similar function is required, and it was recommended in code review to rather duplicate the short function instead of making it more complex. I'm dropping the CN part here since it wasn't used anyway, and if used in the future, the function could be duplicated for CN as well. Related: SYS#5560 Change-Id: I77b0ef33f94c401d24f38eb8d79e1007234e0ab4 |
||
---|---|---|
contrib | ||
debian | ||
doc | ||
include | ||
src | ||
tests | ||
.gitignore | ||
.gitreview | ||
AUTHORS | ||
COPYING | ||
Makefile.am | ||
README.md | ||
configure.ac | ||
git-version-gen | ||
osmoappdesc.py |
README.md
osmo-bsc-nat
OsmoBSCNAT masquerades multiple BSCs behind one. It is part of the Osmocom Open Source Mobile Communications project.
Homepage
The official homepage of the project is https://osmocom.org/projects/osmo-bscnat/wiki
GIT Repository
You can clone from the official osmo-bsc-nat.git repository using
git clone git://git.osmocom.org/osmo-bsc-nat.git
There is a cgit interface at https://git.osmocom.org/osmo-bsc-nat/
Documentation
User Manuals and VTY reference manuals are optionally built in PDF form as part of the build process.
Pre-rendered PDF version of the current "master" can be found at User Manual as well as the VTY Reference Manual
Mailing List
Discussions related to osmo-bsc-nat are happening on the openbsc@lists.osmocom.org mailing list, please see https://lists.osmocom.org/mailman/listinfo/openbsc for subscription options and the list archive.
Please observe the Osmocom Mailing List Rules when posting.
Manual Testing With osmo-dev
With osmo-dev it is possible to build all Osmocom components for a full test network with OsmoBSCNAT, and run the network on your PC. Set up the make directory as described in osmo-dev's README, then build components with:
$ make cn-bsc-nat
Set up a network as described in osmo-dev's net/README, then put the following in your configuration to let it run osmo-bsc-nat with one virtual BSC, BTS and MS (can be used next to a real BSC/BTS/MS):
BSC_COUNT=2
BSC0_CODEC_LIST="fr2"
BSC1_CODEC_LIST="fr2"
BTS1_RUN_IN_OSMO_DEV=1
STP_RAN_IP="127.0.0.2"
MS_RUN_IN_OSMO_DEV=1
Contributing
Our coding standards are described at https://osmocom.org/projects/cellular-infrastructure/wiki/Coding_standards
We us a gerrit based patch submission/review process for managing contributions. Please see https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit for more details
The current patch queue for osmo-bsc-nat can be seen at https://gerrit.osmocom.org/#/q/project:osmo-bsc-nat+status:open