>Also, any idea why Ascend dynamic bandwidth allocation doesn't work on the
>Livingston? I'm calling from a Pipeline 25, and if I call a PM3, it never
>grabs a second channel, even if the bandwidth usage requires it. The
>same connection works correctly when connecting to an Ascend 400T.
Maybe because its "Ascend" dynamic bandwidth allocation and not
"Livingston" dynamic bandwidth allocation? Ie. it is proprietary. And as
for the non-proprietary BACP (Bandwidth Allocation Control Protocol),
Livingston does not support that either although Ascend does. Livingston
does support On-demand dialing which brings up the link when traffic
warrants it, but then it depends on the idle timer to drop the connection
and it appears to be "all or nothing". Interestingly, if you are using a
Livingston - Livingston connection with the proprietary Liv. multilink
protocol, you can set a high water mark of bytes before bringing up
another dial connection. But this is not the case with ISDN and MPPP,
there is no dynamic bandwidth allocation going on. Its two different
approaches to the same thing. For the Ascend it is designed for
dynamically calling, assigning bandwidth, etc. But, it can be too much
during configuration when all you want to do is bring up the connection by
dialing and keep it up. On the other hand... Livingston does that well,
it just doesn't do dynamic bandwidth yo-yoing up and down.