mirror of
https://gitea.osmocom.org/cellular-infrastructure/osmo-mgw.git
synced 2025-10-23 08:12:01 +00:00
04da5e5e98
Return the CI string allocated by the MGW and sent back during CRCX ACK. So far the CI that identifies one connection of an MGW endpoint is "hidden" behind mgcp_conn_* API. This CI string is however very interesting, for logging, to be able to correlate with MGCP messages in network traces. For osmo-bsc, there is an upcoming mgw_endpoint_fsm that will log the CI string using this function. Change-Id: I0c802c0cc3fa0aae9558bd7f15aad1cb9a8b12b2
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