> This first output is from one of three PM3's that all do the same. Note the SQL Statement and there is nothing going into the online in Emerald
> The second output is from A Computone PowerRack and its working fine. Online is updating. Both are setup the same in Emerald.
> Response Time: 261
> radrecv: Request from host c76ba402 code=4, id=231, length=94
> Acct-Session-Id = "0B00052F"
> User-Name = "farwest1"
> NAS-Identifier = 188.8.131.52
> NAS-Port = 31
> NAS-Port-Type = Async
> Acct-Status-Type = Start
> Acct-Authentic = RADIUS
> User-Service = Framed-User
> Framed-Protocol = PPP
> Framed-Address = 184.108.40.206
> Acct-Delay-Time = 0
> SQL Statement: UPDATE CallsOnline Set AcctStatusType=2, CallDate=GetDate() WHER
> E NASIdentifier='220.127.116.11'
This is a bug in RadiusNT 2.2.10 which was fixed in RadiusNT 2.2.16. The
code incorrectly interprets an accounting session ID starting with a alpha
character or 0's follwed by alpha characters as a restart and is clearing
the NAS entries in the CallsOnline table.
> Acct-Session-Id = "715.02.0"
atol("715.02.0") is not zero, so it works fine.
BTW, this is still beta issues, and posting to the list is like
torcher those people who don't have RadiusNT 2.2. <GRIN>