Osmocom Media Gateway (RTP proxy and RTP/E1 gateway)
https://osmocom.org/projects/osmo-mgw
cc0b97e197
If an MGCP operation on one conn of an endpoint fails, no longer carry out other pending requests for that endpoint. Only allow pending DLCX to be sent. If the caller schedules two CRCX at the same time, the first CRCX is sent with a wildcarded endpoint name like "rtpbridge/*@mgw". Only when the OK for that returns an allocated endpoint, will the second CRCX be sent, using that actual allocated endpoint name. But, if the first CRCX fails, then we should not send another wildcard CRCX, but rather assume both as failed. Since a failed MGCP message means that the endpoint becomes unusable / undefined and typically deallocates directly, we can actually discard all other pending requests except for DLCX. Change-Id: Icb1d485224bb486b84eff6329f0bd95932e63246 |
||
|---|---|---|
| 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