malicious call trace setup

[SpelingChampeon]

Option 61C Rls 5.5 with a spare TTY port:

I have a situation where I need to turn Malicious Call Trace on quite a few phones (approx 25) with the users being the "administrators".

I want to make this a one-way printout to a laptop in an office, so that no one has the capability to talk back to the switch. The laptop has PCP installed, and anytime the TRACE button is hit on any of the phones, they can just stroll over to the laptop and see what the CLID is of the call being traced. They should never have access to the PBX (I dont even want the IDLE to be accessed), nor would I have to worry about calls at all hours of the day to decipher what they are seeing.

Any help would be appreciated.. thanks!

 

[GHTROUT]

What about something like this?

http://pro-key-lock.100dof.qarchive.org/

If you set a TTY as "PRT" I've seen systems react bad when the systems recieves input from a keyboard - not sure about recent releases though.

[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators

 

[SpelingChampeon]

GH, thanks for the reply...I will look into the key-lock program.

If you dont mind...define "react bad".. are you talking about an INI or just a bug code spitting out? If its something that is truly ridiculously bad (such as an INI), I would be suprised it hasnt been addressed yet.

 

[GHTROUT]

I had a switch INI when I was playing with ADAN PRT setting. Generally, you have ADAN TTY and not ADAN PRT

INI'd every time I pressed a key. It was probably an X-11 rls 19 system, but I am not sure about newer releases.

[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators