Actions
Bug #2884
openCall Control timers are very long and not configurable
Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
01/27/2018
Due date:
% Done:
10%
Resolution:
Spec Reference:
Description
I just noticed that there are some timers for which the 3GPP specs don't provide defaults, but we use some really large compiled-in value that cannot be modified.
T310 is one such example. It is invoked if (in a MT call) CALL CONFIRMED is received from the MS, but there's never nay ALERT, CONNET or DISCONNECT following. We are setting it in libosmocore to 180 seconds, which is super large. I doubt anyone would make a call and then wait three minutes for any indication that it rings on the other side. For comparison, the MS-side timer for the same situation is specified at 30s.
Actions
