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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

RAS and Call Logger

Status
Not open for further replies.

frankieg

Technical User
Oct 1, 2002
147
0
0
GB
Hi All

I have a strange problem with my call logging. When you dial the remote-access number the output from the Avaya only shows the number dialled outward. Incoming calls are not logged at all. All the rest of my switch is logged incoming and outgoing with no problems. I know that RAS is a security issue but these guys know that and want it.
i have attached my Sys CDR settings. PS I use a data module for CDR.
Thanks for any advice

CDR SYSTEM PARAMETERS

Node Number (Local PBX ID): CDR Date Format: day/month
Primary Output Format: customized Primary Output Endpoint: 20630
Secondary Output Format:
Use ISDN Layouts? n
Use Enhanced Formats? n Condition Code 'T' For Redirected Calls? n
Modified Circuit ID Display? n Remove # From Called Number? n
Record Outgoing Calls Only? n Intra-switch CDR? n
Suppress CDR for Ineffective Call Attempts? y Outg Trk Call Splitting? y
Disconnect Information in Place of FRL? n Outg Attd Call Record? y
Interworking Feat-flag? n
Force Entry of Acct Code for Calls Marked on Toll Analysis Form? n
Calls to Hunt Group - Record: member-ext
Record Called Vector Directory Number Instead of Group or Member? n
Record Called Agent Login ID Instead of Group or Member? n
Inc Trk Call Splitting? n
Record Non-Call-Assoc TSC? n Call Record Handling Option: warning
Record Call-Assoc TSC? n Digits to Record for Outgoing Calls: dialed
Privacy - Digits to Hide: 0 CDR Account Code Length: 15

CDR SYSTEM PARAMETERS

Data Item - Length Data Item - Length Data Item - Length
1: date - 6 17: dialed-num - 23 33: auth-code - 13
2: space - 1 18: space - 1 34: return - 1
3: time - 4 19: in-trk-code - 4 35: line-feed - 1
4: space - 1 20: space - 1 36: -
5: sec-dur - 5 21: in-crt-id - 3 37: -
6: space - 1 22: space - 1 38: -
7: cond-code - 1 23: calling-num - 15 39: -
8: space - 1 24: space - 1 40: -
9: attd-console - 2 25: vdn - 5 41: -
10: space - 1 26: space - 1 42: -
11: code-used - 4 27: bcc - 1 43: -
12: space - 1 28: space - 1 44: -
13: out-crt-id - 3 29: ppm - 5 45: -
14: space - 1 30: space - 1 46: -
15: code-dial - 4 31: acct-code - 15 47: -
16: space - 1 32: space - 1 48: -

Record length = 131

 
Are your remote access lines actually going through the switch? Or are they stand alone?

If you are refering to the remote access line to the switch itself, (commonly called the INADS line) in most cases those are set up directly to the port, so you won't see anything in CDR. You can do a list history to see what has been coming in there.

You could take and set up the line to come through the switch if you want to see it using cdr.
 
No it is remote access on the Avaya. ( Disp remote-access)
It is not INADS.
 
Hi Frakieg,
Try to create a vdn number first and on its vector, route the caller that will use the remote acces to the remote access number. This is what I used in our center so that I know when this vdn number appeared on my Call accounting reports, only means that they use the remote access feature of my switch. Here is the sample vector I made:
splay vector 43 Page 1 of 3 SPE B
CALL VECTOR

Number: 43 Name:
Lock? n
Basic? y EAS? y G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? y
Prompting? y LAI? n G3V4 Adv Route? y CINFO? y BSR? y Holidays? y

01 wait-time 2 secs hearing ringback
02 route-to number 81346 with cov n if unconditionally
03 stop
04
05
where 81346 is my remote access number.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top