malicious call trace 3

[gbriggs]

I have an opt 11c rel 24.24. I have an annoying call that keeps comming in to the front desk phone on key 8 the main line. This is an m2616. I need to know if there is a way to trace out the call comming in to the phone?

 

[mars1947]

In ld 11 add MCTA in cls and assign a key xx TRC where xx is the key number.

 

[mars1947]

Then all you have to do is push the button of that key and it should print in the switch.

 

[srmega41]

There are a couple of things you could do.

1) Put a TRC Key on your set, with CLS set to MCTA. Then, when a call comes in, the receptionist presses that key and the call data is sent to the Maintenance terminal.

2) If you can be told when the call is coming in, do a TRAC in LD 80 on the DN
.TRAC 0 xxxx (Where xxxx = the DN the calls comes into) You can also do this at a TN level.

LD 80 is all call trace info, there may be other things you can do there, but these are the two I am familiar with.

Hope this helps,

Scott M.

 

[gbriggs]

Thank you all I will try this out...

 

[acewarlock]

When I hit the TRC KEY all I get is


MCE CUST00 RM000 005 *TN033 0 00 07 12:31:28 17/11/2005 ANI# <3=;

 

[gbriggs]

I set up the phone and got the same results:
MCE CUST 00 RM040 010 *TN005 0 00 00 12:16:54 17/11/2005 ANI# <5=;. Do I need to turn on incomming cdr?

 

[srmega41]

Possible. If you CLID via PRI, you should get additional info. I know the trace is set up to tell you where the call came from. Can you try the TRAC in LD 80? I know I use that, and it provides TN's of trunks, as well as called/calling ID info.

Scott M.

 

[gbriggs]

TRAC works, Problem is I do not know when this guy is calling. That is why she needs the TRC key.

 

[srmega41]

Yep, that is the issue. I do not know any way to incorporate the two, other than starring at a terminal, seeing a TRC envoked, and the doing a TRAC right then.

Maybe someone else has another suggestion???

 

[acewarlock]

Kind of a usless feature, I have other things to do then sit at the monitor waiting for a message that might never come.

 

[johnpoole]

if your running procomm

proc main

 waitfor "MCE CUST " forever
 transmit "trac 33 7^M"
endproc

if the switch is logged in and in ld 80, the caller is always hitting the same tn? 33 7.. that would work, i have auto log off disabled so this script would do a trace for you. but ANI# <5=;. makes me thing your not getting ani (automatic number id) is not, we are wasting your time.. i have had users transfer the call to 911.. seems to cause them to stop.. i would dump cdr to a term, if it's that hot

john poole
bellsouth business
columbia,sc

 

[acewarlock]

I get caller ID on my phone so that shouldn't be a problem.

 

[HASAGO]

You could use the automatic trac command - might help?

LD 80
.ENTC 33 7 100 (where the TN is 33-7)

100=1 hour (maximum is 23 hours)

 

[johnpoole]

that's a good call, does that work on opt 11's? used to it didn;t

john poole
bellsouth business
columbia,sc

 

[HASAGO]

There was an earlier issue with using the ENTC command on Option 11 but was resolved with a patch if same issue that you are referring too. The patch is only available for some earlier software releases and available on the Nortel library. See below further information...

Cannot use enhanced trace and get error TRA306.

You need to insert patch p10892_1 as required.

System is an Option 11C with Release 22.08D
Multi-User logon is enabled in the Configuration Record

In Overlay 80 the command

ENTC CC UU XXYY where XXYY is the duration in hours and mins

System responds with the message
TRA306 (Time duration out of range)

Notes;
Code exists for Enhanced Call Trace from X11 R20
with Multi-User Login for Option 11.