Osmocom Media Gateway (RTP proxy and RTP/E1 gateway)
https://osmocom.org/projects/osmo-mgw
a729db62a9
Reduce the number of hex chars generated as Connection Identifier from 32 to 8. According to RFC3435 2.1.3.2 "Names of Connections", the maximum length is indeed 32 characters, but there isn't really a benefit of using IDs of that size. That, and: A specific SCCPlite MSC is seen to be able to store conn IDs of up to 8 hex characters of length. If given more than that, it will later send 'ffffffff' as ID, e.g. in the DLCX message, causing mismatches and rejected DLCX. Conn IDs need to be unique only within the context of one endpoint, so producing 32 characters of ID is far beyond overkill, especially if we currently expect exactly two IDs per endpoint. Notice that the maximum length of conn ID that can be handled by the message parsing and composition doesn't change, only the length that an osmo-mgw will generate upon CRCX does. Related: OS#3507 Change-Id: Ia290c22a91fca0e5aa44515fca6df00064aff100 |
||
|---|---|---|
| contrib | ||
| debian | ||
| doc | ||
| include | ||
| m4 | ||
| src | ||
| tests | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| AUTHORS | ||
| COPYING | ||
| Makefile.am | ||
| README | ||
| README.vty-tests | ||
| TODO-RELEASE | ||
| configure.ac | ||
| git-version-gen | ||
| libosmo-legacy-mgcp.pc.in | ||
| libosmo-mgcp-client.pc.in | ||
| osmoappdesc.py | ||
README
About OsmoMGW ============= OsmoMGW originated from the OpenBSC project, which started as a minimalistic all-in-one implementation of the GSM Network. In 2017, OpenBSC had reached maturity and diversity (including M3UA SIGTRAN and 3G support in the form of IuCS and IuPS interfaces) that naturally lead to a separation of the all-in-one approach to fully independent separate programs as in typical GSM networks. OsmoMGW was one of the parts split off from the old openbsc.git. It originated as a solution to merely navigate RTP streams through a NAT, but has since matured to a Media Gateway implementation that is capable of streaming RTP for 2G (AoIP) and 3G (IuCS) GSM networks as well as (still not implemented at time of writing) transcoding between TRAU, various RTP payloads and IuUP. The OsmoMGW program exposes an MGCP interface towards clients like OsmoMSC and OsmoBSC, and receives and sends RTP streams as configured via MGCP. The libosmo-mgcp-client library exposes utilities used by e.g. OsmoMSC (found in osmo-msc.git) to instruct OsmoMGW via its MGCP service. The libosmo-mgcp library exposes MGCP server utilities used by e.g. OsmoBSC-NAT (found in osmo-bsc.git) to navigate RTP streams through a NAT. (At time of writing, this is still called libosmo-legacy-mgcp.) Find OsmoMGW issue tracker and wiki online at https://osmocom.org/projects/osmo-mgw https://osmocom.org/projects/osmo-mgw/wiki