Thanks for the info.
I think the content is normally much less than 250 chars but the doc's I
have from CISCO do say "Max 256 bytes"
They did this for the (IMHO) *WRONG* reason, so that a brain damaged RADIUS
that won't support VSA's can work!
Yuck! Just give me a list of VSA's to add and keep all this as separate
Attributes in the Calls Table!
Oh Well...
By the way if you want the poop on this email me direct and I'll put you in
touch with the guy at CISCO who wrote the paper.
Perhaps you can convert him to the *RIGHT* kind of Radius? : -)
Thanks again!
=============
Denny Figuerres
dennyf@inreach.com
-----Original Message-----
From: radiusnt-request@iea-software.com
[mailto:radiusnt-request@iea-software.com]On Behalf Of Dale E. Reed Jr.
Sent: Tuesday, March 28, 2000 3:24 PM
To: radiusnt@iea-software.com
Subject: Re: [RadiusNT] Ascend Max3000 and Radius Accounting
Denny Figuerres wrote:
>
> Btw: anyone worked with Cisco VoIP radius packets with Radius NT?? They
> have some goofy deal where they
> Stuff up to 256 bytes in to Acct-Session-ID. Wonder if aside from
modifying
> the table if it would make RadiusNT blowup or anything?
We'd definately reject 256 bytes in ASID, since an attribute data can
only be 254 bytes in RADIUS. :)
Otherwise, if it was 254 or less, RadiusNT shouldn't have a problem with
it.
--Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart