Real Time Ascend Maling List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) New TNT and CSMX cards
I'm getting the same type of errors on my CSM3 boxes right now, I was told
by Ascend that this is a documented problem and it happens because the DSP
is getting assigned the call before it's properly
reset, So basically the shelf controllers believes the DSP to be available
to take the digital call when in reality the DSP is still crippled and is
not able to take the call.
(However, I question this reply from Ascend and await more of a descriptive
answer considering I have additional DSP's on the box that should be
handling the call instead of a DSP that just dropped one). From what I
understand they will call-route to the most idle DSP. If this is true then
I shouldn't be seeing these errors.
(These of course the DSP's on the CSM3 box), Is your HDLC card in slot
1/3?
Jason Nealis
Director of Internet Operations
RCN
----- Original Message -----
From: William R. Charnock <charnock@fastlane.net>
To: Paul Rolland <rol@oleane.net>
Cc: <ascend-users@bungi.com>
Sent: Wednesday, April 07, 1999 3:13 AM
Subject: Re: (ASCEND) New TNT and CSMX cards
> I have done that and it seems to be working -- but here is another
problem
> -- on all my TNT's, I get the following message after a short while of
the
> box being up:
>
> Apr 6 21:17:32 fw-tnt1 1/3: _openNewChannel [MBID 1378] CANT OPEN HDLC
> CHANNEL(s) name <>, wanIndex 2, callId 0, mode 0
> Apr 6 21:18:01 fw-tnt1 1/3: _openNewChannel [MBID 1381] CANT OPEN HDLC
> CHANNEL(s) name <>, wanIndex 2, callId 0, mode 0
> Apr 6 21:22:59 fw-tnt1 1/3: _openNewChannel [MBID 1383] CANT OPEN HDLC
> CHANNEL(s) name <>, wanIndex 2, callId 0, mode 0
> Apr 6 21:24:49 fw-tnt1 1/3: _openNewChannel [MBID 1385] CANT OPEN HDLC
> CHANNEL(s) name <>, wanIndex 2, callId 0, mode 0
> Apr 6 21:25:11 fw-tnt1 1/3: _openNewChannel [MBID 1387] CANT OPEN HDLC
> CHANNEL(s) name <>, wanIndex 2, callId 0, mode 0
> Apr 6 21:29:00 fw-tnt1 1/3: _openNewChannel [MBID 1386] CANT OPEN HDLC
> CHANNEL(s) name <>, wanIndex 2, callId 0, mode 0
> Apr 6 21:29:32 fw-tnt1 1/3: _openNewChannel [MBID 1390] CANT OPEN HDLC
> CHANNEL(s) name <>, wanIndex 2, callId 0, mode 0
>
> When this occurs, I can no longer accept inbound ISDN calls. I have to
> reset the HDLC-2 card to get the server to accept ISDN calls. Is Ascend
> aware of this problem? Is there a fix coming?
>
> --
> William Charnock
> CTO, FastLane Internet Services
> (817)-429-5263
> netadmin@fastlane.net
>
> On Wed, 7 Apr 1999, Paul Rolland wrote:
>
> > Yes, do it, it works...
> >
> > Anyhow, I'd like to take opportunity of this message to send out a big
> > question :
> > As it seems there are more and more people with TNT, HDLC-2 and CSMX
> > cards, could you please tell me, either on the list or privately,
> > what you think of these and TAOS 7.0.4.
> > Do you have problem ? Strange messages coming out of the box ? New
> > trouble with users ? Connection problems ?
> >
> > Regards,
> > Paul
> >
> > Paul Rolland, rol@oleane.net
> > France Telecom Oleane/Direction Technique/Directeur
> > France Telecom Oleane/Technical Direction/Director
> >
> > --
> >
> > Please no MIME, I don't read it - Pas de MIME, je ne le lis pas
> > Please no HTML, I'm not a navigator - Pas d'HTML, je ne suis pas un
navigateur
> >
> > "The best way to predict the future... is to create it !"
> >
>
> ++ 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>