You must also look at the parameters to see if they are using DNAction or Agent State. Depending on the definition they can overlap each other if I remeber it correct
There is a LOGIN Table which cab be made available, which shows an absolute LOGIN and LOGOUT for each Agent, from which you can calculate the LOGIN time. That would seem easier to me than having to SUM all of the different states in order to determine LOGIN…
Vic, don’t bother trying to add it up. It’ll never equate. If
T Inbound+ T Consult+ T Hold+T Wait + T Ringing+ T Dialing+T Not Ready+ T Internal + T Outbound+T Work+ T Off Hook are all defined with Subject = AgentStatus then it might be close to T Login, but never exact.
The easier way like Tony mentioned is to activate the StatServer applications LOGIN table. Run the Login init script and query the table. It’s actually quite accurate since it gives a timestamp of login and logout occurences.