John,
Thanks for the insight into this problem. I really appreciate it. It
sounds like you know your ascend equipment.
Thanks again for all the help!!
At 10:15 PM 11/2/99 +1300, you wrote:
This is a known issue with the MAX and TNT. I had this discussion several
months ago and managed to
This is a known issue with the MAX and TNT. I had this discussion several
months ago and managed to work through it with Mike and an Josh Bailey and
Engineer for Ascend. Here was the outcome:
Sending stop only for failed connections is customary Ascend behaviour -
it's been done for many year
Hello Cortney -
On Tue, 02 Nov 1999, Cortney Thompson wrote:
> Hi all,
>
> I am a new radiator user, and I have been testing radiator for about a week
> now. Well I am finally looking at our results in depth and I have noticed
> that raidator reported a LOT of Null's in our accounting databa
We get a lot of them with TNT's and Max's... One thing I have noticed about
them - there is never a session time associated with them - often there is a
"Ascend-PreSession-Time = xx" but never a Session-Time attribute...
Looking at the "Ascend-Disconnect-Cause" attribute, and looking at the data
Hi all,
I am a new radiator user, and I have been testing radiator for about a week
now. Well I am finally looking at our results in depth and I have noticed
that raidator reported a LOT of Null's in our accounting database. We are
running radiator on Windows NT across ODBC to MS SQL 7.0. E
