Osmocom Media Gateway (RTP proxy and RTP/E1 gateway)
https://osmocom.org/projects/osmo-mgw
Pau Espin
ca280a1a84
The following sequence of events was seen frequently in a osmo-mgw instance running on the field with heavy traffic: """ endpoint:rtpbridge/1@mgw CRCX: creating new connection ... mgcp_network.c:236 endpoint:rtpbridge/1@mgw CI:1C8CCFA9 Failed to send dummy RTP packet. """ Allegedly, that happens because at CRCX time the remote address may still not be known, hence we end up trying to send a dummy rtp packet to, for instance, host 0.0.0.0 port 0, which will of course fail. Let's avoid sending it if the address is not yet known. Similary, same issue could be seen during MDCX, since at MDCX we don't necessarily need to have a valid addr+port (there could be several MDCX and only last one set it). Finally, the keepalive timer also needs the check, since it iterates over all connections, and it could be that some is still not fully configured. Related: SYS#5498 Change-Id: I8ceafda691146823b12232b4a804b4ce74acbdc8 |
||
|---|---|---|
| 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-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. Find OsmoMGW issue tracker and wiki online at https://osmocom.org/projects/osmo-mgw https://osmocom.org/projects/osmo-mgw/wiki