>I finally got syslog going to track terminate causes. Although it's only
One thing to keep in mind is that the syslog values only show part of the
story. It also includes things like people just calling your pool with a
handset. If your pool gets a lot of wrong numbers, this could jack up the
values. But over a few thousand calls, its hard to imagine too many of
these unless you are next to some common number. You should also compare
the results you get to what sort of stats you see on authenticated calls as
well by analysing the RADIUS figures. Another thing to keep in mind, is
that if the amount of 'wrong numbers' stay at a relativly constant rate,
you can use the before and after figures to help you evaluate the success
or failure of any ComOS upgrades. When we went from 3.8 to 3.8.2, we did
one box, and the change in syslog stats was only marginally different, but
statistically significant. It gave us that much more confidence to upgrade
our entire pool.
---Mike
Mike Tancsa (mdtancsa@sentex.net)
Sentex Communications Corp,
Waterloo, Ontario, Canada
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>