Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How to trace incoming calls 1

Status
Not open for further replies.

1norteltech

Programmer
Dec 19, 2007
129
US
We seem to have a rash of incoming calls to various departments at different times of the day from a perve. I collect raw CDR data, but I am not able to see any calls to the extensions at the times I am being told that this has occurred. I'm told the calls are made directly to the (DID) extensions. Our operators use ACD, so if the calls go through them, I don't know where the calls are transfered to. Is there any way to configure the CDR output to show every incoming call and where it finally terminates?

Opt. 61 Rls. 25.40

TYPE CDR_DATA
CUST 0

TYPE CDR_DATA
CUST 00
CDR YES
IMPH NO
OMPH NO
AXID NO
TRCR YES
CDPR YES
ECDR NO
PORT 9
BCAP NO
CHLN 0
FCAF NO
 
Things to consider:

Incoming Caller ID for CDR is set in the "PARM" of LD17 CFN (it's the CLID prompt). It's not in CDR_DATA of LD15. This just in case you are not getting CLID for inbound.

Check the trunks routes and make sure all of them have CDR and OAL=YES + INC=YES

It's possible the call is internal. Unless you have station CLS=ICDR, you won't see those calls.

If the perp/perv tends to call certain people more than others, you could give them a TRC Key with CLS MCTA. Then you'd catch the "Trace" in TTY history. Those users should also be the first to get CLS=ICDA



~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
 
Ooops, I mean ICDA Internal CDR Allow

(not ICDR)

~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
 
Thanks for the response. here's my route and parm. I thought I had it set up correctly to capture the CDR for incoming calls, but i am not certain. I am also at the mercy of the end user when it comes to time and extension, As far as internal, I have not set any sets to ICDA in CLS and default is ICDD. I never had a need to track internal CDR. Maybe something to concider. Do the settings I have look correct to you? And do I have the correct options in the CDR_data?

Any help appreciated.

TYPE RDB
CUST 00
ROUT 29
DES DID_2_WAY
TKTP DID
NPID_TBL_NUM 0
SAT NO
RCLS EXT
DTRK YES
DGTP PRI
ISDN YES
MODE PRA
IFC ESS5
SBN NO
PNI 00001
SRVC NNSF
NCNA YES
NCRD YES
CHTY BCH
ISAR NO
CPUB OFF
DAPC NO
BCOT 0
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
RANX NO
SRCH RRB
TRMB YES
STEP
ACOD 2929
TCPP NO
PII NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC YES
DCNO 0
NDNO 0 *
DEXT YES
DNAM NO
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510
GRD 896
SFB 3
NBS 2048
NBL 4096
TFD 0
DRNG NO
CDR YES
INC YES


PAGE 002

LAST YES
QREC YES
OAL YES
AIA NO
OAN NO
OPD YES
NATL YES
MUS YES
MRT 11
MR NO
RACD NO
EQAR YES
NTOL ALOW
ITOL DENY
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
TTBL 0
ATAN NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
AACR NO

PARM
LPIB 1000
HPIB 1000
500B 1000
SL1B 250
NCR 3000
MGCR NULL
CSQI 200
CSQO 200
TUBO NO
CFWS YES
PCML MU
ALRM YES
ERRM ERR BUG AUD
DTRB 100
TMRK 128
FCDR OLD
PCDR NO
TPO NO
TSO NO
CLID YES
DUR5 NO
MLDN YES
MARP YES
FRPT NEFR
DCUS NULL
MSCL 350
PMSI
MANU PMS1
PMCR 0
PORT NONE
NDIS 20
OCAC NO
MTRO MR
SBA_ADM_INS 000
SBA_USER 000
BCAP SPEECH
NORTEL_BRAND NO
 
Yes, everything looks good to me. You are getting every record (except internal of course). If you are just capturing the data into text, make sure you have a really good text editor with a "search results" capability. Not just "find".

I use Ultra-Edit version 7.2 (old but the lightest weight version I know of) I can search through a 30 meg text file and generate a "results list" of every appearance of a certain string - all in a matter of seconds. 30 meg can be millions of lines.


~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
 
BigI his first post had the CDR_DATA. The second post was the RDB + the PARM (which only holds CLID entry for CDR). So your account must be debited :)

~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
 
If there is a major problem and he is calling a few numbers then put a TRC key on the phone and you will get all the calling info on the terminal and in the history file.

Signature===========================================

Aastra Authorized Reseller
 
Thanks again for your responses. And yes, the data is a simple hyperterm capture to a .txt file and search is the simple find (unfortunately al I have at this point). I agree I may need to put the TRC key on some phones, but there is no set pattern to the calls. First it was the 4th floor nusing unit, then the OB unit, and today it was ER, 3rd floor, and random other areas. A lot of the sets are 2008 with no vacant keys, and the people with 2616's with displays can't tell me the number from the call. I appreciate everyone looking at my setup, I thought it was right, but wanted to CYA.
 
best bet is to have the called party do a transfer to a security phone..

we had a bomb threat at a gov building a few years back.. i did a entc on one set.. it was hfa and auto answer.. all calls transfered to 5555.. even if the security guard was asleep, all the information on the call was captured..

the person was caught.. seems he wanted his day in court delayed.. so instead of paying a fine, he called in 2 threats.. after the 2nd one (internal) the locals turned him over to the fbi.. people are so clever

john poole
bellsouth business
columbia,sc
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top