Clicking Noise during inbound or outbound calls.

[gopalmohan]

I am getting complaints from our agents on the floor that they are getting clicking noise after they are connected to clients. Is there any way to test PRIs T1 to see if something is wrong with PRI or is it card.

Any way of testing for sure where this is coming from. We have about 14 T1 and its hard to test each of them.

Please help me out.

Gop

 

[bigindian65]

First thing I would test is who has their cell phone laying next to their acd set.

Mato' Was'aka

 

[gopalmohan]

That is good tip, I have checked them all. They are experienced agents and it just started happening this Monday and all of sudden we have list of callers going up with clicking issue. Its not an interference in the line its like then we call or client call, rings works fine but as soon as you are connected with clients this clicking noise of click.. click.. click.. click.. take over the call and nothing can be heard from both sides.

I am thinking its PRI T1s or Trunk.

Any idea where to start please?

 

[hawks]

Check your clock source and make sure your clock is not in free run. If you get slips then you will hear a clicking on the lines during conversatios.

 

[acewarlock]

LD 60 LCNT and post here




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[gopalmohan]

Thank you so much acewarlock.
Here is lcnt from ld 60 for your kind perusal.

>LD 60
DTI000
.LCNT

PRI TRK LOOP 2
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -001
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 3
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -001
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 12
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -001
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 13
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -001
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 18
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -001
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 19
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -001
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 28
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -000
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 29
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -000
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 34
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -000
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 35
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -000
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 44
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -001
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 45
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -001
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 50
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -001
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 51
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -000
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 60
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -001
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000


PRI TRK LOOP 61
TRSH CNT:
BPV -000
SLIPD -000
SLIPR -001
CRC -000
LOSFA -000
OS_BPV -000
OS_LOSFA-000
OS_YEL -000

 

[phonz1]

in LD73, prt your ddb and post and then in Ld60 post an ssck please

 

[allenmac]

In order to test the Circuit, you will need a TBERD. This will tell you very quickly if you are having issues with the T1/PRI, and will also tell you where the problems are coming from (Telco or PBX).

your LCNT printout looks OK, but that is only telling you what is coming into your T1/PRI's from the CSU.

 

[gopalmohan]

REQ PRT
TYPE DDB

PREF 2
SREF 18

TRSH 00
RALM 3
BIPC 2
LFAC 3
BIPV 3 2
SRTK 5 30
SRNT 15 3
LFAL 17 511
SRIM 1
SRMM 2
ICS


.SSCK 0
ENBL
STANDBY
GROUP 1
SIDE 0
CLOCK CONTROLLER - LOCKED TO LOOP 2
PREF - 2
SREF - 18
AUTO SWREF CLK - ENBL
NO ERROR

DTI000
.SSCK 1
ENBL
CLOCK ACTIVE
GROUP 1
SIDE 1
CLOCK CONTROLLER - LOCKED TO LOOP 2
PREF - 2
SREF - 18
AUTO SWREF CLK - ENBL
NO ERROR
.

 

[phonz1]

ok, are you currently running on side 1?

 

[gopalmohan]

I don't know, how can I check please?

 

[bigindian65]

stat in ld 137

Mato' Was'aka

 

[gopalmohan]

It gave me CMDU 0 is active and CMDU 1 is Standby..
Thank you Bigindian65

 

[phonz1]

ok, you need to swap cores or clocks, side 1 core should run with clock 1, get those together and see if the problem goes away.

LD 135

. scpu

after the swap in ld 135 yet, stat cpu and see if side 1 is active, then test for the clicking

 

[gopalmohan]

Thank you phonz1, our system is redundant system. May be that is why the CMDU1 is active. I just checked it this morning CMDU0 is active now but there is no change in clicking noise.

Regards.

Gop

 

[phonz1]

stat your clocks and and your cores and make sure that clock 0 is active and core 0 is active..... then maybe I'd look at a pattern, are the sets that complain all on one card, in one shelf???

 

[hawks]

What phonz1 is saying is the CMDU should match the Clock Card. So now if you do SSCK in LD 60 then it should show that SIDE 0 as being Active and 1 as Standby.

 

[gopalmohan]

They are both on clock 0, as for the card its going to one cabinet but from there its nightmare.. any idea of help to sort this out will be highly appreciatead.

Cheers.

Gop

 

[phonz1]

okay... it could be a 3PE or a Per Sig, seems like the clocks have been eliminated. I would order some and replace one and test before replacing the other

 

[tnphoneman]

get the users to write down the trunk acod and member number when they get the clicking. Maybe you can nail it down to one span. They may have to put the caller on hold and pick them up again to get this info.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.