Bug #4863
openT3212 is unclear in config/vty
0%
Description
In the config file or vty the command timer vlr T3212 accepts a value in minutes.
Inline help suggest that this is a "3GPP compliant timer number", However timer 3212 is expressed in units of 6 minutes.
Updated by fixeria over 3 years ago
Inline help suggest that this is a "3GPP compliant timer number", However timer 3212 is expressed in units of 6 minutes.
This is how it's encoded in System Information messages, i.e. 'on the air'.
In the config file or vty the command timer vlr T3212 accepts a value in minutes.
However, in the VTY it's configured in minutes (as stated in the help).
Updated by keith over 3 years ago
Thanks fixeria for the response.
This is not something I want to take up much of your time with, BTW, it is also something of an example for educational purposes for how to make tickets and resolve issues within osmocom community...
All the same, it is unclear to me still what you mean by "the help" as it was unclear to us yesterday when I started talking about timers in a workshop the first question that came up was.. "so are these timers in seconds or minutes or what..." to which i answered ah ha! you see... you have to look up the timer in question in the specs to know.. but, I said; Let's see what the vty tells us.. and here I was expecting it to be explicit.
if i go to the msc config node and type timer vlr and [ENTER} then I see
vlr: T3212 = 60 m Subscriber expiration timeout (default: 60 m)
I actually just discovered that now. is that what you refer to?
If I do timer vlr ? then:
[TNNNN] T- or X-timer-number -- 3GPP compliant timer number of the format '1234' or 'T1234' or 't1234'; Osmocom-specific timer number of the format: 'X1234' or 'x1234'.
No mention of units there.
Anyway, not a huge deal, I guess network admins should know what they are doing, and we should not try to describe each timer in the vty help!
All the same, maybe our inline vty descriptions could be more explicit about units?