Re: Odd PRI problem on 81c
- From: "Chris Romero" <nospamto-cromero-please@xxxxxxxxxx>
- Date: Mon, 10 Apr 2006 09:03:52 GMT
Don't feel alone. I once had a failure of a DMS100 card in a Bell South
C.O. in Raleigh. Took me more than three weeks to get them to replace the
card. I even had a T1 test set and two site visits from Bell (gone) South
techs. Real PIA.
I don't doubt the similar things happening in other areas
The customer is sometimes insane, but you can always count on a L.E.C. to be
obstinate and superior!
--
Sincerely,
Chris
cromero at romero dot org
"RonB" <ronb02@xxxxxxxxxxxxxxx> wrote in message
news:Xns979F8EEEB640Cezboard1lycoscom@xxxxxxxxxxxxxxxx
On Tue 04 Apr 2006 11:31:13p, RonB <ronb02@xxxxxxxxxxxxxxx>, wrote:
I was sent out to a site where they've recently noticed that six of
their PRI circuits (all in the same group) are showing "FE DSBL" on a
few of their channels -- one loop *had* quite a few reporting FE
DSBL, but Verizon has cleared most of that circuit while testing. In
most of the loops it only effects the first channel. What's really
odd is that these channels are working (they have no problems with
dropped calls etc.). When I STAT the channels they show IDLE. When I
direct access them with a maintenance set, I get dial tone and I can
call out. When they're busy, I can TRAD them and get the call record
and they show BUSY when STATed. So the problem seems to be a bogus
error report. Verizon Core Group also sees an FE DSBL (or equivalent
report) from their side, but they also note that the channels are
working.
I think the CO switch is a Lucent -- but, so far, no hard
confirmation. They've got the D channels set to NI2, but CO_TYPE is
set to STD. Our in-house engineer thinks that this should probably be
set to ATT instead *if* the CO switch is a Lucent, but he's reluctant
to screw around with a switch that is working, especially since it's
scheduled to go down in a couple weeks for... some kind of
mainenance... I wasn't told why exactly. The PRIs do come through
CSUs and this is Rel 4. The switch was installed in November and no
one noticed this problem until a couple weeks ago -- but that doesn't
necessarily mean the problem didn't exist from the start. The onsite
tech just got back from school and was experimenting with some of the
STAT commands that he had learned there.
At any rate, has anyone ever heard of this problem? It's the first
time I've ever seen something like this. Thanks for any ideas.
Problem solved. Bell Atlantic (aka Verizon Core) hadn't turned the
B-Channel Messaging Service on. Once they added the feature to the PRIs
everything cleared up in a short time (and they could actually see the
status of the B-Channels where, before, everything looked fine to
them). They said that they had had this problem before with Nortel
Option switches. It took a while to get to someone who would actually
listen -- several open tickets -- but once it finally got to the right
tech it was easy.
--
RonB
"There's a story there...somewhere"
.
- Follow-Ups:
- Re: Odd PRI problem on 81c
- From: RonB
- Re: Odd PRI problem on 81c
- References:
- Odd PRI problem on 81c
- From: RonB
- Re: Odd PRI problem on 81c
- From: RonB
- Odd PRI problem on 81c
- Prev by Date: Re: Startalk Lines don't drop
- Next by Date: Handset/Headset volume
- Previous by thread: Re: Odd PRI problem on 81c
- Next by thread: Re: Odd PRI problem on 81c
- Index(es):
Relevant Pages
|