Hello, To do what you want you add this to your <SessionDatabase SQL> clause:
AddQuery insert into RADONLINE (USERNAME, NASIDENTIFIER, NASPORT, \ ACCTSESSIONID, TIME_STAMP, FRAMEDIPADDRESS, NASPORTTYPE, \ SERVICETYPE, STATIONID) values ('%n', '%N', 0%{NAS-Port},\ '%{Acct-Session-Id}', %{Timestamp}, '%{Framed-IP-Address}',\ '%{NAS-Port-Type}', '%{Service-Type}', '%{Calling-Station-Id}') And modify your table to include the 'STATIONID' column ofcourse. Another way to solve the stale sessions problem is to use accounting updates, 'alive' packets. Cheers, Nicolai On Wed, 2003-06-25 at 19:18, Herman verschooten wrote: > Hi, > > Is there an easy way to extend the on-line check with the callerid? > > > > We use Radiator to authenticate from different ADSL-providers. One of > these frequently drops STOP-packets. Don’t ask me how, but we lose a > lot of them… Start en Alive, no problem, but Stops seem to have other > engagements. > > > > This of course means that the user’s state remains on-line even after > they disconnect. The NASPort is quite useless in this case, since the > Redback chooses a new port when the customer redials. When we used > RadiusNT I wrote a complex solution using triggers and stored > procedures on SQL to delete the record from the online-table when the > request came from the same NAS/CallerID for the ADSL-users. Now I > need a similar system on Radiator, but I have not yet found how to add > the callerid to the RadOnline table. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.