Project

General

Profile

Actions

Bug #5553

closed

dynamic T3113 has no reasonable upper bound

Added by laforge almost 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
A interface
Target version:
-
Start date:
05/06/2022
Due date:
% Done:

100%

Spec Reference:

Description

With sufficiently high simulated paging load, I can drive T3113 to insanve values like >= 580 seconds

20220506140458094 DPAG DEBUG (msc=0) Paging: subscr-IMSI-262420000003717: (bts=64) Paging request: T3113 expires in 584 seconds (paging.c:382)

or even

20220506140550472 DPAG NOTICE (msc=0) Paging: subscr-IMSI-262420000004929: (bts=55) Paging request: T3113 expires in 746 seconds (paging.c:382)

This of course doesn't make sense and just amplifies a paging overload situatoin by making it longer than it would otherwise persist.

I'm not sure if anythinh > 60s would make any sense in practice?


Related issues

Related to OsmoBSC - Bug #5552: no overall limit of paging requests at BSC levelResolvedpespin05/06/2022

Actions
Actions #1

Updated by laforge almost 2 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 50
Actions #2

Updated by laforge almost 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

Applied in changeset commit:osmo-bsc|b6222f28a069d66ec8081730e5066bf153ab7e4b.

Actions #3

Updated by laforge almost 2 years ago

  • Related to Bug #5552: no overall limit of paging requests at BSC level added
Actions #4

Updated by laforge almost 2 years ago

  • Status changed from Resolved to In Progress
  • % Done changed from 100 to 50

not sure why redmine thought it was merged

Actions #5

Updated by laforge almost 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

Applied in changeset commit:osmo-bsc|d952e88fa5f5875185f35db0b5b9ea9bfea5ee6c.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)