(RADIATOR) Incredibly high Acct-Session-Times

[Frank Danielson]

We had a similar situation with accounting data from a 3Com Total Control
chassis. What we noticed was that these abnormally large numbers occurred
when the disconnect cause was 0 or 1 and calls that ended normally had a
disconnect cause of 2. In this case it was due to a call setup failure and
the call disconnected before it had a chance to authenticate. I ended up
writing a hook that set the time to zero if the call had an abnormal
disconnect cause and an impossibly large session time. 
Here is an example of what I did ->

<Handler>
	PreProcessingHook sub {\
		my $time=${$_[0]}->get_attr('Acct-Session-Time');\
		my
$disc_cause=${$_[0]}->get_attr('Disconnect-Cause-Indicator');\
		if (($disc_cause < 2) && ($time > 999999)) {\
			${$_[0]}->change_attr('Acct-Session-Time',0);\
		}\
	}
	<AuthBy XXXX>
	</AuthBy>
</Handler>

If you examine your data you will probably find a similar pattern that you
can detect.

Frank Danielson
[Infrastructure Architect]

voice:407.515.8633
fax:407.515.9001

ClearSky Mobile Media, Inc.
301 E. Pine St. Suite 400
Orlando, FL 32801
USA
 



-----Original Message-----
From: Richard Grantham [mailto:Richard.Grantham at bactel.com]
Sent: Thursday, May 29, 2003 10:52 AM
To: radiator at open.com.au
Subject: (RADIATOR) Incredibly high Acct-Session-Times


Hi all,

I think this only happens when a call does not connect but I've
noticed something strange with regards to call duration.  I think this
is illustrated well in this output listing from our accounting database:

ACCT_SESSION_TIME
-----------------
                4
       1054176189
       1054176307
       1054176350
       1054176384
       1054176426
       1054176522
       1054177499
       1054177560
       1054177767
                7
       1054179354
       1054179448
       1054196686
       1054197106
       1054198442
       1054199147
       1054200785
       1054200912
       1054201263
       1054201288

The sensible numbers are 'real' Acct-Session-Time values.  I'm
wondering, where does Radiator get these HUGE values from?  They
seem to increase would I be right in thinking they are based on the
system time?  Why are they not 0?  Can I force them to be 0?

Richard
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.