<snip> > I know this has come up before, and in a perfect world, where * was the > primary app, you don't need RADIUS. In enterprise environments where > RADIUS accounting is already embedded into other aspects of the > workflow, it would be beneficial. > > Understand....* boxes are in real live actual production now. Once you > leave the vacuum of the lab, there are going to be things like this that > come up. And many will be for good reasons. Others will be for > crappy, legacy reasons. Both scenarios are valid in the real world. >
Can someone give me an idea exactly what things are intended to be tested via RADIUS, or some other AAA system? Are we talking about building SIP/IAX/H323 entries from RADIUS? At this point, I'm not really worried about call detail, as that's something that * already can dump to a database, it can be adapted to dump back to any service. (Unless this is really the primary objective of the whole RADIUS discussion.) ----- Andrew Thompson http://aktzero.com/ Your eyes are weary from staring at the CRT. You feel sleepy. Notice how restful it is to watch the cursor blink. Close your eyes. The opinions stated above are yours. You cannot imagine why you ever felt otherwise. _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
