Read this email , and in the interest in providing better integration
between our product and RadiusNT I would be more than happy to provide any
information you need to aid the process.. Just sing out the info will
come..
Regards,
Andrew Hall.
Mgr. Network Systems Engineering - Carrier (ANZA).
3Com Corp.
"Dale E. Reed Jr." <daler@iea-software.com> on 11/05/98 16:10:36
Please respond to RadiusNT@iea-software.com
To: RadiusNT@iea-software.com
cc: emerald@emerald.iea.com (bcc: Andrew Hall/AU/3Com)
Subject: Re: USR Total Control
Michael Whisenant wrote:
>
> 1.1 I have had to increase the lenght of the field for call ports
to
> extend to 4 digits. The modems in slot 10 will report as 101 to 1024.
If
> you have 11 DSPs then you would get multiple users logged to the same
port,
> ie Slot 1 modem 11 is reported as 111 and Slot 11 modem 1 is also
reported
> as 111. Then what?
Are you referring to Servers.Ports table for Emerald? That field is
practically irrelevant, excpt for when creating/re-ported a NAS. The
most important fields, Calls.NASPort and ServerPorts.Port, are both
type integer.
I would guess hope that it would correctly align the numbers. For
example, 1001 for 10/1 and 101 for 1/1, etc. Then there shouldn't
be an issue. If not, there isn't anything you can do about it.
USR, err, 3Com, has such a looser site. I've never been able to
find the technical information I needed (plenty of marketing, but
nada for support. Just search for "RADIUS" on their FAQ search
and you'll get a whole two entries returned!) on their website.
Trying to download the documentation is even worse, since they only
let "privledged" people get to that. Geeze.
Ok. Off my soap box. Try running a query like this against
your calls table to see what kind of ports are being recorded.
Send me the list and I'll try to make something of it.
Select DISTINCT NASPort