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

CDR date and time

Status
Not open for further replies.

AvayaDude

Technical User
Sep 10, 2003
61
US
I'm running netcat and everything appears to be running fine. My txt file keeps growing as the day goes along. I have one small issue, the date and time in my txt file are showing up as 000432 (for the date) and 8224 (for the time). It has been this all day. Here is an extract of my txt file:
000432 8224 49256 3309268851 40149 3309268851 01410 7002
000432 8224 49358 4696288263 40358 4696288263 00317 7004
000432 8224 49365 2484102626 40129 2484102626 00017 7008
Here is my system parameters:
display system-parameters cdr Page 1 of 2
CDR SYSTEM PARAMETERS

Node Number (Local PBX ID): CDR Date Format: month/day
Primary Output Format: customized Primary Output Endpoint: CDR1
Secondary Output Format: customized Secondary Output Endpoint: CDR2
Use ISDN Layouts? y
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? y
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 Agent ID on Incoming? n Record Agent ID on Outgoing? y
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
Data Item - Length Data Item - Length Data Item - Length
1: date - 6 17: line-feed - 1 33: -
2: space - 6 18: - 34: -
3: time - 4 19: - 35: -
4: space - 6 20: - 36: -
5: vdn - 5 21: - 37: -
6: space - 6 22: - 38: -
7: calling-num - 10 23: - 39: -
8: space - 6 24: - 40: -
9: dialed-num - 18 25: - 41: -
10: space - 3 26: - 42: -
11: clg-num/in-tac - 10 27: - 43: -
12: space - 3 28: - 44: -
13: sec-dur - 5 29: - 45: -
14: space - 3 30: - 46: -
15: in-trk-code - 4 31: - 47: -
16: return - 1 32: - 48: -


Does anyone have any idea why this is happening?

Thanks
 
Did you ever fix this? I am having the exact same issue.
 
Are you using CDR1 or 2? I wonder if there is a difference or a bug that causes cdr2 to report differently.

 
I re-configured everything from scratch and replaced the PC that was running netcat. I'm also now running it from CDR1 instead of CDR2. Everything is great now. No more date/time issues.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top