Project

General

Profile

Actions

Feature #3429

closed

idea: auto-cleanup endpoints after long period of inactivity?

Added by neels over 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
07/28/2018
Due date:
% Done:

100%

Spec Reference:

Description

To avoid a scenario where osmo-mgw maintains open endpoints for a voice stream that long ceased without the mgw being told, we might want to automatically close down rtpbridge/* endpoints if we have seen no MGCP message and also not a single RTP package for a long time. A long time could be 10 minutes, or also as low as half a minute.

What happens when osmo-bsc or osmo-msc crash hard with RTP streams open? Do osmo-bsc / osmo-mgw send a wildcard DLCX for all endpoints? Maybe not a good idea in case several osmo-bsc and/or osmo-msc share the same MGW?

(Inspired by an IRC question about osmo-mgw saying "Not able to find a free endpoint")


Related issues

Related to OsmoMGW - Feature #3507: allow shorter Connection Identifier 'I:'Resolvedneels08/28/2018

Actions
Related to OsmoMGW - Feature #3508: compare Connection Identifier 'I:' case insensitivelyResolvedneels08/28/2018

Actions
Related to OsmoMGW - Feature #3509: match MGCP "I:" Connection ID also when leading zeros are omittedResolvedneels08/29/2018

Actions
Related to OsmoMSC - Feature #3655: Introduce self-destruction timer for SS/USSD connectionsResolvedfixeria10/16/2018

Actions
Related to OsmoBSC - Feature #3659: handover during LCLS directly between BTSsStalleddexter10/17/2018

Actions
Related to OsmoMGW - Feature #3783: Make conn-timeout compatible with LCLSResolvedosmith02/06/2019

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)