Re: (ASCEND) Max 4000 2nd PRI doesn't partition correctly

To: <mel@becknet.com>, <ascend-users@bungi.com>
Subject: Re: (ASCEND) Max 4000 2nd PRI doesn't partition correctly
From: "Kevin A. Smith" <kevin@ascend.com>
Date: Tue, 03 Feb 1998 14:31:52 -0800
In-Reply-To: <1325684329-1999296@mail.becknet.com>
Sender: owner-ascend-users@max.bungi.com

At 03:55 PM 2/2/98 -0800, mel@becknet.com wrote:
>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?

Configuration. What do you have in the T1 line configuration for each of
the PRIs?



Kevin


++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

References:

(ASCEND) Max 4000 2nd PRI doesn't partition correctly

From: <mel@becknet.com>

Prev by Date: Re: (ASCEND) Who runs IDSL ?!?
Next by Date: Re: (ASCEND) Who runs IDSL ?!?
Prev by thread: (ASCEND) Max 4000 2nd PRI doesn't partition correctly
Next by thread: Re: (ASCEND) Max 4000 2nd PRI doesn't partition correctly
Index(es):
- Main
- Thread