You are right I was talking about the Ascend-terminate-cause.
What I meant in the calls table there is only AcctTerminateCause
which logs the Acct-Terminate-Cause for the Portmaster but not
the Ascend-Terminate-Cause for the MAX. If they are two seperate
columns how to check for the terminate cause in emerald for people
how were logged onto the MAX.
>
> William Salame wrote:
> >
> > We are running radiusNT 2.2 with emerald 2.1.11. We are using
> > Ascend MAX 4060 with 2 E1's 30 B-channels each.
> > We have three querries if any one have any suggestions.
> >
> > 1. Emerald does not log the terminate cause.
> > Radius is runing in debug mode and showing the terminate cause
> > for both Portmaster Livungston such as
> > Acct-Terminate-Cause = User-Request and for the MAX4000 such
> > as Acct-Terminate-Cause = 185. Emerald logs the terminate cause for
> > the Portmaster but not for the Livingston.
> > The Ascend MAX was upgraded with the latest firmware last week.
>
> Are you sure the max is reporting Acct-Terminate-Cause or
> Ascend-Disconnect-Cause? I assume you mean it logs the PM and not
> the MAX?
>
> > 2. Emerald shows only the first 54 ports On Line, but doesn't show
> > the last 6 ports. All login informations are logged to the SQL
> > database except they do not appear On-line
>
> Go into the Emerald Admin, Config Radius, Server Ports tab and
> see if 55-60 are there. You may have to add them, as the
> Ascend Type might only do the T1 ports (and miss the last 6
> ports). It would be like 10125-10130, 20125-20130, etc.
>
> --
> Dale E. Reed Jr. (daler@iea.com)
> _________________________________________________________________
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today | http://www.iea-software.com
>
> ----------------------------------------------------------
> RadiusNT Mailing List lists@iea-software.com
-- William SalameOperations ManagerKNOWLEDGE by Designmailto:william@kbd.com.au