We're having a hard time with a PM-3 on a CT1. All of our
others PM3's are on PRIs, and we've had very few problems with them.
Unfortunately, we're upgrading to PM3's at some of our other locations
where PRIs are not available, so I'd like to get the problems
resolved. At this point, I'm not sure if it's a PM problem or a phone
line problem, so any help would be *greatly* appreciated!
The Situation
A PM3, with 3 10 modem cards. ComOS version 3.5.1b20. The lines
are FSX loop start (ESF, B8ZS). I'd prefer to have wink start
from what I've read in the list, but phone companies,
tariffs... don't get me started on that ;-)!
The Problem
Customer busy signals, rings with no answers, no rings, and great
difficulty in general connecting even when there are *many* ports
open.
Supporting Information
First, from what I've read, wink start is preferable in the
C. T1's (but for financial reasons this isn't available to
us).
Secondly, there looks to be some strangeness in our modems. We
have 30 (m0 though m19, and m30 through m39 -- I'll probably never
figure out the numbering convention). They all show good except
for m18 and m18, which show DOWN. I'm not sure if the modems will
show down only when they're broken, or maybe the lines are bad --
any insight here would be appreciated.
The really strange thing, though, is what the modems claim to be
doing. I have modems that claim to be attached to ports that are
in fact idle. I also have modems that claim to be attached to
ports that *other* modems are in fact attached to (as shown be a
show all). For example:
pm3-bky-1> show m30
State: ACTIVE
Active Port: S2
...
pm3-bky-1> show m8
State: ACTIVE
Active Port: S2
...
...where a show all show s2 to be attached to m8, not m30.
Also, the lines appear to be pretty dirty, but that's hard to be
sure of. In 20 days of uptime, the one T1 has taken CRC errors
(92), Sync errors (88), and Bipolar errors (65992). The other T1
is a bit worse than that. Now, it doesn't look good, but those
errors tally fast when a line goes down, so it *could* be that the
line went down for a while and the line took all of those errors
at once.
We're running 2.5.1b20 because we were told that this "fixes" the busy
problem with CT1's, but that's not what we're seeing!
Thanks in advance.
--Mark