Real Time Ascend Maling List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) PRI does not fill up after reboot



The story that we received from Ascend in Australia was that the E1 load of
code was not sending disconnect/connect information to the switch on warm
boots.  If you did a cold boot, the channels would come back.  This was
found in version 6.1.7, & supposedly fixed in 6.1.24 (wasn't in the end).
No issues (like this) have been seen by us in any version 7 load.

A
----- Original Message -----
From: Jill Bell <j.m.bell@bradford.ac.uk>
Cc: <ascend-users@bungi.com>
Sent: Wednesday, 12 May 1999 18:25
Subject: Re: (ASCEND) PRI does not fill up after reboot


>
>
> Phillip Vandry wrote:
> >
> >
> > After a Max reboots, either normally or abnormally, the PRIs come back
up,
> > but they refuse to fill up. After n channels are filled up, the number
> > rings busy. n may be anywhere from 2 or 3 to 20 or more.
> >
> > And it's always the same channels. As a fictitious example, I may see
> > after a reboot that channels 1-5 work, and 10, 15, and 20-23 (for a
total
> > of 10 channels). The rest look idle according to the Max but they can't
> > receive calls.
> >
> > If one of the calls on the 10 working channels drops, another call will
> > come in to replace it, but the remaining channels juts don't get used.
> >
> > The problem clears after several consecutive reboots (after the reboot
that
> > caused the problem in the first place).
> >
> >
> I saw similar problems with release 6.1.24. I upgraded to 7.0.4 and am
> now working ok.
>
>  This is how I described my problem in a mail message to this list....
>
> "I have a 4060, a 4000 and a 6000 all now running 6.1.24 Each has 2 PRIs
> and 64 modems - we have no ISDN calls.
>
> They are connected to an Ericcson MD110 telephone switch running
> software level 7.2. The interfaces are DPNSS which I think is the same
> as DASS2
>
> We waited for 6.1.24 because of modem retraining problems in earlier
> releases.
>
> All looked well until about a week after the upgrade to 6.1.24 when the
> PRIs stop working at random. The telephone switch supervisor says that
> the PRI is in 'blocked' mode. Sometimes the whole PRI goes into the
> blocked mode sometimes it is individual channels."
>
> ----------------
> The following is an extract from this mail list which I thought was the
> same problem as mine..
> >I recently installed a MAX 6000 on our hunt group of Onramp 30 E1 lines.
> >The rest of the RAS are Portmaster III, since installing the MAX dialup
> >customers are occasionaly receiving busy tones.  When not using the MAX
> >everything is fine therfore I figure it has something to do with this.
> >
> >Unfortunantly I havnt been able to check what is going on as I havnt
> >received any exact times of this happening.  However all a our modems
have
> >never been filled.
> >
> >When I replace the MAX with another PM3 using the same lines everything
is
> >fine.
>
> We had this with 6.1.7 and 6.1.24.
> Ascend told me these versions for 6000 had a "broken" E1 code (note that
> we
> don't use T1. I think Australia uses E1 too).
> I installed 7.0.4 and everything is fine.
>
> -------------------
>
> Hope this helps
>
> Jill Bell
> Bradford University
> UK
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd: <http://www.nealis.net/ascend/faq>
>


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