Change in osmo-mgw[master]: mgcp_ctrl: add functions to inspect trunk usage

pespin gerrit-no-reply at
Wed Jul 7 09:05:57 UTC 2021

pespin has posted comments on this change. ( )

Change subject: mgcp_ctrl: add functions to inspect trunk usage

Patch Set 2:

(1 comment)

So I think both Neels and I have the feeling osmo_stat probably fits better than using the CTRL interface for this purpose, am I wrong? Other opinions welcome.

>From dexter: "This is needed for TTCN3 testing. Would osmo_stat work with that. Also this is not a rate counter, this is a fixed value at a certain point in time."

That's what osmo_stat_item are for, to provide information of a fixed value at a certain point in time. That's what we use for instance to provide information about how many logical channels are in use, how many are available, etc. So same can be done here imho. 
Commit Message: 
PS1, Line 11: operators to monitor the MGW usage and also simplifies TTCN3 tests
> Its more for testing with TTCN3, at least that is what I need it for. […]
well, rate_ctr are for tate counters, and osmo_stats are for stats ;)

Both are available through statsd and also can be checked by TTCN3, we already have APIs there and tests using it to validate the values.

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

Gerrit-Project: osmo-mgw
Gerrit-Branch: master
Gerrit-Change-Id: Ib8b5a6e733f521828647742085cad8eccb3e715b
Gerrit-Change-Number: 24822
Gerrit-PatchSet: 2
Gerrit-Owner: dexter <pmaier at>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: pespin <pespin at>
Gerrit-CC: neels <nhofmeyr at>
Gerrit-Comment-Date: Wed, 07 Jul 2021 09:05:57 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: neels <nhofmeyr at>
Comment-In-Reply-To: dexter <pmaier at>
Gerrit-MessageType: comment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gerrit-log mailing list