|
Joined: Jun 2004
Posts: 33
Member
|
Member
Joined: Jun 2004
Posts: 33 |
Any feedback on relevant troubleshooting techniques would be much appreciated.
My customer has a MICS 4.1 with PRI, using XO Communications as PRI provider. They recently reported experiencing intermittent clicking and loud choppy static on telephone calls, and they say they've had it for "quite some time".
They have not been able to narrow it down to any particular stations, or inbound vs. outbound calls, etc. and so I suggested that they contact XO and have them do a test on the PRI circuit.
XO reports the following: "the lines tested clean all the way to the Network Interface Unit. We ran a quasi test and the customers' CSU was returning errors, specifically 62 pattern slips and 1 CRC error, but no frame or bit errors."
Any thoughts on how I should be troubleshooting this from our side? I appreciate anyone's assistance as I'm pretty new to testing these types of circuits...
|
|
|
Nortel Phone System Service in Canada
Do you need a Nortel Phone System technician or specific Nortel parts?
Atcom to the rescue! Our telephone techs have qualified experience servicing and troubleshooting Nortel CICS, MICS, & BCM telephone systems.
Service in Canada from sea to sea.
|
|
|
Joined: Nov 2001
Posts: 81
Member
|
Member
Joined: Nov 2001
Posts: 81 |
This can still be a bad NIU card or possibly a bad extended demarc - You will need to go out there and give XO a hard loop at the extended demarc and see if they are still getting errors if so make sure the extended demarc is clean. This would be my first step.
|
|
|
|
Joined: Jan 2002
Posts: 2,328
Moderator-Comdial
|
Moderator-Comdial
Joined: Jan 2002
Posts: 2,328 |
I had this issue about a year ago. Site had 2 pri's. Sprint and Bell provided. The problem was always on Bell's pri. The Bell CO tester I had finally retermed his end and the problem cleared up. Clicking and static on a pri is usually caused by poor terminations somewhere along the route.
|
|
|
|
Joined: Jun 2004
Posts: 33
Member
|
Member
Joined: Jun 2004
Posts: 33 |
<font face="Verdana, Arial" size="2">Originally posted by Mark Smith: You will need to go out there and give XO a hard loop at the extended demarc and see if they are still getting errors if so make sure the extended demarc is clean. This would be my first step. </font> Thanks Mark. Could you please elaborate on the "hard loop"?
|
|
|
|
Joined: Jun 2004
Posts: 33
Member
|
Member
Joined: Jun 2004
Posts: 33 |
Thanks again to both of you for the thoughts...any idea about internal error reporting on the MICS I might be able to access?
|
|
|
|
Joined: Jan 2002
Posts: 2,328
Moderator-Comdial
|
Moderator-Comdial
Joined: Jan 2002
Posts: 2,328 |
A hard loop is a physical loopback device installed to "loop" the signal back to the sender. The sender is either the telco or your system. If you loop to the telco, they can run all manner of tests. You can run loopback tests on your ICS, too. Its under maintenance. Make your own loopback devices both plug and jack. Pin 1 to 4 and 2 to 5. You must use 8 pin devices! There are some troubleshooting procedures in the installer manual. Alarm codes are also explained.
[This message has been edited by jwooten (edited June 06, 2004).]
[This message has been edited by jwooten (edited June 06, 2004).]
|
|
|
|
Joined: May 2004
Posts: 187
Member
|
Member
Joined: May 2004
Posts: 187 |
you most likely have a telco problem, have the provider run loop back test. You may have bit errors. If someone decide to tap into the same wire that feeds this circuit this problem starts. Splicers do this when they are working pairs in the area. If you have a T1 watcher you can monitor for errors also. When the telco enters the circuit you will see errors. good luck.
|
|
|
Forums84
Topics94,422
Posts639,465
Members49,819
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
228
guests, and
39
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|