Incoming "Malicious" Call Problems

[paradigm]

I'm trying to sort out a problem that keeps occurring on our phone system once every few days to seemingly random incoming calls.
I know what the Malicious feature does. It goes under names like Malicious Caller Identification, Malicious Call Trace (MCT) and Caller Activated Malicious Call Trace.
My problem is I don't know how to turn it off or disable it on our OXO.

What happens, is a call comes in as normal on our SDSL/ISDN20 line through Telstra (Australia) and goes into Attendant Group 8. Phones in this Attendant group after picking up a call with the handset, every so often (it seems randomly) display the message "Malicious" and disconnect the new call.
I've tried to find common occurrences as to who, where and when the call is set as Malicious but I haven't found any similarities or possible reasons to the cause of the problem. Maybe someone everytime presses a key on the other end of the call? I don't know. I seem this hard to believe if it happens once every 40 odd calls.

Within Features In Conversation, I have removed the Malicious feature. (As mentioned in viewtopic.php?p=10233#p10233)
I have also consulted our PBX provider, but they haven't got word from the Business Partner site on a solution.

If anyone has had this problem, I would really appreciate your feedback or thoughts.
Regards,
David

[zanex]

have you got MCT activated by telstra - it is a subscribed service from them

[paradigm]

That's a very good question. I'll find out now.

[Jigger]

this problem used to come up alot with the systems that got sent out via Telstra / TBS....

I had 2 sites with the feature not used and telstra had it turned off... both sites worked perfect after a LOLA..not sure why it occurs

[tot3nkopf]

See MCID_KYP debug label in Noteworthy addresses.

Regards.

[paradigm]

I contacted our Telstra guy and he wrote back:

Nothing I can see on your lines from our end that could be causing this.

Tot3nkopf, in Debug Label MCID_KYP is set to 0. I also noticed that there is a MctAvaiTim variable that is set to 82 00 HEX.
Would changing MctAvaiTim help fix the Malicious issues we're having? Or do you think its still Telstra that is the problem?

[tot3nkopf]

I contacted our Telstra guy and he wrote back:

Nothing I can see on your lines from our end that could be causing this.

Tot3nkopf, in Debug Label MCID_KYP is set to 0. I also noticed that there is a MctAvaiTim variable that is set to 82 00 HEX.
Would changing MctAvaiTim help fix the Malicious issues we're having? Or do you think its still Telstra that is the problem?

I don't know. In Romania Malicious call is not (yet I hope) supported by TELCO, so my experience in this is nill. However you can make tests with that labels. Remember that some modifications of the labels rquire a worm reset of the OXO in order to be taken into account.

Regards.

[zanex]

never trust what telstra says.....

[dmode]

seen this at a R510.018.004 site. Log in case and check the MCID_KYP label but to no avail. Finally upgrade to R610.007.002, it disappear.

[paradigm]

According to our Software Version, we're running 3EH30382ARAA ALZAU610/007.004. So later than R610.007.002..
Maybe I should talk to our Telstra guy again.?