Change in osmo-bsc[master]: osmo_bsc_main: integrate MGW pooling into osmo-bsc

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at

pespin gerrit-no-reply at
Mon Aug 23 14:24:39 UTC 2021

pespin has posted comments on this change. ( )

Change subject: osmo_bsc_main: integrate MGW pooling into osmo-bsc

Patch Set 10:

File doc/manuals/chapters/mgwpool.adoc: 
PS10, Line 7: machnies. Until osmo-mgw includes multithreading support, it may also be used ot
PS10, Line 8: scale-out to multiple cores on a single host."
Remove character: " 
PS10, Line 11: the pool will automatically assign the call to the MGW with the lowest load.
hint/idea: It may make sense to defie some "maximum call load" config or similar to vty, so one can calculate % of load when taking the decision. That's in case you have different hosts (different HW) serving calls running osmo-mgw. 
PS10, Line 41: local host ip-addresses or different ports. When OsmoMGW is installed from
IP addresses 
PS10, Line 64: each MGW must be different. Otherwise it won't be possible to distinguish the
should be 
PS10, Line 72: calls.
do we have a vty command to avoid establishing new calls on a mgw node? (EDIT) Self-answer: yes. it would be nice to put a link to an anchor to the section below explaining it. 
PS10, Line 76: The VTY implenets a 'show mgw-pool' command that lists the currently configured
File include/osmocom/bsc/gsm_data.h: 
PS10, Line 1363: 		/* Single MGCP client configuration under msc node (also required for
I would avoid maintaining different structs from previous versions. Let's always use a pool and put there only 1 mgw if needed. 
File src/osmo-bsc/osmo_bsc_main.c: 
PS10, Line 890:         mgcp_client_single = mgcp_client_init(bsc_gsmnet, bsc_gsmnet->mgw.conf);
AS I said, let's rather fill the pool always from the VTY?

Maybe here, if the pool is empty, create one and put it into the pool.

To view, visit
To unsubscribe, or for help writing mail filters, visit

Gerrit-Project: osmo-bsc
Gerrit-Branch: master
Gerrit-Change-Id: I8f33ab2cea04b545c403a6fe479aa963a0fc0d0d
Gerrit-Change-Number: 25123
Gerrit-PatchSet: 10
Gerrit-Owner: dexter <pmaier at>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: daniel <dwillmann at>
Gerrit-Reviewer: laforge <laforge at>
Gerrit-Reviewer: osmith <osmith at>
Gerrit-CC: pespin <pespin at>
Gerrit-Comment-Date: Mon, 23 Aug 2021 14:24:39 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gerrit-log mailing list