(RADIATOR) Timestamp Attribute Handling...

[Ray Van Dolson]

Just a comment... I ran into this recently -- we proxy from Radiator to our
Billmax Radius server and the Billmax server was getting confused by the
presence of the Timestamp attribute.  Turns out type 103 wasn't defined in
Billmax's Radius server's dictionary file.  Adding it solved the problem, but
perhaps I should have stripped this attribute before proxying it in the first
place...

Ray

On Fri, Jan 21, 2005 at 01:28:51PM +0200, Rickard Ekeroth wrote:
> I have noticed that Radiator adds a 'Timestamp' (103) attribute to any
> incoming accounting request (it does not seem to happen for access
> requests). As I understand this 'Timestamp' attribute is the current time
> adjusted for any 'Acct-Delay-Time', if present. This is all ok.

--
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.