RE: (ASCEND) Pipeline 85 Cause Code Question

[Randy Snow <snow@apassmore.com>]

I'm hashing this out with the phone company now.  To be on the safe side, I
brought my Lucent :) Pipeline 85 to the office and replaced my Ascend
Pipeline 50 with it.  The dial-in numbers are exactly the same, so all I did
is change the SPIDS and the My Num parameters.  Works 100% at 64K/128K.
This eliminates the possibility that the Pipeline is the problem.

SWBell called me last night and reported that the line was fine.  I guess
they ran some test from their CO.  I refused to accept it and told them to
look into it further.  It is confirmed though, I get a Cause Code 01
everytime I try to dial a number at 64K speeds.  If I set the Pipeline to
64K service and force a 56K connect, this also occurs.

Data Svc=64K
Force 56=Yes

I did the inside wiring for the router, and I'm using one pair of a 4 pair
CAT-5 solid cable.  This cable goes straight from the phone box on the
outside of the house, to the router.  Length is about 30 feet.

Well, at least I confirmed the Pipeline does indeed work at 64K or 128K with
both channels active.  If I find the problem, I'll try and fire off an email
to the list to let everyone know what it is.  Just for reference. :)

-----Original Message-----
From: Phillip Vandry [mailto:vandryp@psi.ca]
Sent: Monday, March 27, 2000 5:32 PM
To: Dana Hudes
Cc: ascend-users@bungi.com
Subject: Re: (ASCEND) Pipeline 85 Cause Code Question



Still, the phone number either exists or doesn't. It doesn't exists
depending on the type of call. If the call type were wrong or
unsupported he should be getting something else, like 65
(Bearer service not implemented)


-Phil


> its been a while but memory says there is something about voice over data.
> A configuration parameter which would set the voice bit on the call.
> This is not valid at 64k only 56k. You can have 56k ISDN w/o voice bit
> I believe.
> Check the line parameters on the pipeline
>
> On Mon, 27 Mar 2000, Randy Snow wrote:
>
> > Thank you Phillip.  Considering the fact that my office Pipeline 50
works
> > just fine with the same number, I'll assume it's the phone companies
problem
> > and give them a call.  At least I know what the message means now. :)
> >
> > -----Original Message-----
> > From: Phillip Vandry [mailto:vandryp@psi.ca]
> > Sent: Monday, March 27, 2000 3:35 PM
> > To: Randy Snow
> > Cc: ascend-users@bungi.com
> > Subject: Re: (ASCEND) Pipeline 85 Cause Code Question
> >
> >
> > > I have a pipeline 85 that works fine at 56k.  When I increase the
speed to
> > > 64k it shoots back the following error:
> > >
> > > Cause Code 01 - Unallocated (unassigned) number
> > >
> > > Testing the unit, packets are successfully transmitted when set to
64K.
> > >
> > > So, what exactly does this error tell me?  I see the 'Unallocated
> > > (unassigned) number' in the manual, but what exactly does this mean?
> >
> > It means it's a wrong number, simply. (The ISDN equivalent of getting
the
> > recorded message "The number you have dialed is not in service" on an
analog
> > line)
> >
> > The fact that the number works at 56K but not at 64K indicates to me
that
> > there's something seriously wrong with your telco's network, or your
ISP's
> > telco's network.
> >
> > -Phil
> >
>
>
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>