Noise in OWS on MX-ONE TSW

[joe201237]

Hi all,
The customer’s Operators (2 OWS in MX-ONE TSW) had strange noises (only beeps without voice and noise ) in incoming internal, external calls & even when there is no incoming calls (beeps on the headset), we taught that it’s probably came from the faulty TMU boards which the operators are connected, but after the replacement with the new boards, the noises doesn’t disappear.
We test all trunks to verify if any lines are broken and also the cabling in the MDF & patch panel, but everything seems ok.
Do you have any idea what is the origin of this issue?
Thanks in advance & best regards.

 

[parnum]

hi

Their extensions not connected to TMU's, it will be digital cards ELU5 or ELU28, you were given some bad advice.

Pls post
OPISPIR=ALL:
OPDDPIR=ALL:

The result BPOS of OPDDP, are they the same card? swap the card

best parnum

 

[joe201237]

Hi parnum,
Thanks first for responding, but I checked, they are not on yhe same card,as printing below:

opddp:dir=all;
OPERATOR DIRECTORY DATA
DIR EQU OCUST TYPE PCM REV
1111 001-0-20-00 - 4 - -
1112 001-0-22-00 - 4 - -

opisp:dir=all;
OPERATOR INSTRUMENT STATUS DATA
DIR ANSW EXTEND AUD LEV MODE LANG
1111 N N N L 0 -
1112 N N N L 0 -

 

[joe201237]

Hi Parnum,
do you have any idea how I can sole this problem please?
thanks in advance.
BR

 

[himdp]

Just for your information, TMU = Tone and Multiparty Unit; Each Operator take two MultiParty channels, so changing the TMU was not such bad advice even though it didn't fix your issue

 

[parnum]

Hi Joe

Try restarting OLP11T, OLP1D, DOM, DOR - unusual fault usually it's the ELU card or the CT Adaptor, a physical problem

Best parnum

 

[joe201237]

Hi Parnum,
How can I restart OLP11T, OLP1D, DOM, DOR?
And if I restart, the system will retart too?

 

[joe201237]

Hi Parnum,
Any help, please.
BR

 

[parnum]

Hi

You need to check the lims the units are in

CNPIP:UNIT=OLP1T;
CNPIP:UNIT=OLP1D;
CNPIP:UNIT=DOM; (result is lim x)

CNPIP:UNIT=DOR; (result is lim x)

If for example CNPIP:UNIT=OLP1T; and CNPIP:UNIT=OLP1D; the result is lims 1,2,3 for each

then restart (but make sure your operators are off-duty first)

RFPUI:UNIT=OLP1T&OLP1D,LIM=1&2&3;
RFPUI:UNIT=DOM,LIM=x;
RFPUI:UNIT=DOR,LIM=x;

As we do not know your software level you may find CNPIP:UNIT=DOM; returns no result, so try CNPIP:UNIT=DOMS1; instead.

Once done, log the operators back on

best parnum

 

[fcpli]

In my humble opinion, starting the PU's won't help. Did this problem arise suddenly or after some kind of change?

 

[himdp]

fcpli, agreed software is unlikely to be the cause here particularly the PUs mentioned. It sounds like a hardware issue. I note that the two operators are in the same 32 group. It might be worth trying to move one of the operators to another magazine and see if that one is OK (LSU/DSU issue). Possibly move OPI to another LIM, if there is one.

 

[parnum]

I did say I believe it's a physical issue but stranger things have happened with operator software,

best parnum

 

[joe201237]

Thanks to all of you for your help, but I'm very confuse wich action should I do?
would you advise me please?
BR

 

[fcpli]

Joe,
Pls answer my question, just to get a clue of what is/was happening

 

[joe201237]

Thanks fcpli,
To answer your question, the problem arise many times a week and still for long time during a day, until the operators couldn't bear the noises.
Of course it happen without doing any programming or changing anything in the system.
I hope that was the answer of your question, otherwise, please give me more details.
BR.

 

[fcpli]

Joe,
So this problem has been there even without any changes in SW/FW or whatever? Then, check your CT adapter(s) revision. If I remember, the lowest rev is R7A for TSW (maybe I am wrong). Can this have something to do with traffic density (high traffic towards the OWS)? Very hard to say, because tracing this is not possible (just a tone not coming from the TSW boards), so my guess is the CT adapter....