> > > It looks like PM2 keep trying to call the same number
> > > 555-2000 to establish the 2nd B channal.
I believe this is proper behavior for Multilink PPP - a Hunt Group is
required at the other end (especially if it is a PM)! :(
> > > It looks like PM2 keep trying to call the same number
> > > 555-2000 to establish the 2nd B channal. Is there any way I can tell PM2
> > > to call 555-2001 to establish the 2nd channal?
I believe that you can put any number of numbers to call separated by
ampersands? Ie:
5552000&5552001
I know the BitSurfrs do this and I'm pretty sure the PMs do it to as well.
> > > When I used another Ascend
> > > to call the Ascend, they allow me to enter 2 numbers and they could
> > > connect at 128K.
How did you do this? I'd love to know so that I can get rid of some hunt
groups (extra $$$s for each line, y'know). What version of the Ascend OS
and what command/menu/incantation to use?
> I just went through this nightmare with a P-75 (5.0A) and Tech Support
> said "We can't get multilink PPP to work" (but they did solve the basic
> config problem). The real answer - and the _only_ way to make this work -
> is to upgrade to the 3.5.1b17 release. I was running 3.5 and figured -
> Hey I'm current; there's only a beta after this! If you read
> release351b17.txt you'll find a section titled: "Improved Multilink PPP"
> and the key phrase "improving interoperability with other vendors".
Odd... I've never had any problem at all with remote P50s calling into PMs
except for the dual B channel problems, which are solved with a hunt group.
Is there something different with the P75?
Now... does 3.5.1b17 allow this without a hunt group, perhaps??? I'd love
for that to be the case.
Later.
Derric
-- Derric Scott Scott Network Services, Inc. P. O. Box 361353 derric@scott.net (205)987-5889 Birmingham, AL 35236