Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) Max 4000 2nd PRI doesn't partition correctly
We just added a second PRI line to a Max 4000, intending that it be used
as a separate dial-in pool for dedicated (nailed) Centrex connections.
Incoming initial calls work fine -- users dialing the first pool dial-in
number get to the original PRI, users dialing the second pool get to the
second PRI. However, when a DBA occurs and the Max negotiates the number
for the remote Pipeline to call for the next 64K channel, the Max is
telling the remote Pipeline to dial into the second PRI! So all DBA
calls end up trying to dial into our (mostly full) second PRI, which
always has its channels nailed up. We don't want the Max to try and
load-balance the two PRIs (which is what it appears to be doing), but I
can't find anywhere in the documentation that explains how to prevent
this. Any ideas?
-mel
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
Follow-Ups: