CDR retrieval?? 3

[ONsiteengineer]

Hi,

I have my S8300 server running CM 3. I have my call accounting via TCP/IP. One time my call accounting went down and the next day it was up and the CDR in that downtime didnt appear in my call accounting. It should appear right because there should be a buffer. How can I retrieve those call logs in that particular downtime?

 

[inerguard]

The buffer only stores a certain amount so there is no guarantee that it would store all of the days information.

If it's gone , it's gone I'm afraid.


[Started on Version 3 software 15 years a go]

 

[ONsiteengineer]

Inerguard, once again thank you. Yes, the buffered records is limited but even that small amount of records didnt appear in my call accounting at the time it was up. Before it was OK. I was getting alarm in my SEC-CDR. Will this affect. Even Im using only the Primary. But Secondary was configured.

These are the error types for my SEC-CDR alarm: 513, 257 and 1281. THanks.

 

[inerguard]

Hi,

The errors are as follows: -

Error Type 257: Link Retry test (#215) failed. An error was detected when setting up the
link. See the preceding section Procedures for Restoring the CDR Link on page 1134 for
resolution.
d. Error Type 513: the CDR physical link is down for one of the following reasons:
? Cable to the CDR output device is disconnected.
? CDR output device is powered off.
? The data extension where the CDR output device connects to has been busied out or
there is a scheduled daily interchange.
1. Check the connectivity of wire and cable among wall jacket, data module, and the CDR
output device.
2. Enter status data extension and verify that the data extension of the CDR output
device is in the in-service/idle state. If the data extension is not available, see Procedures
for Restoring the CDR Link on page 1134 for resolution.
3. Use display system-parameters maintenance to see the start time of daily maintenance.
4. If the error occurs and is resolved during of daily maintenance, it can be ignored.
e. Error Type 1025: the CDR output device is in an off-line state, (for example, due to paper
jam or paper out for a printer device). The CDR link is torn down.
1. Check the CDR output device and act promptly to put it back to on-line state.
2. Enter test cdr-link primary | secondary command to set up the CDR link.
f. Error Type 1281: overflow of CDR records generated in the switch due to the heavy trunk
traffic and low speed CDR output device. If both primary and secondary links are ON, the
secondary link is torn down temporarily for two minutes to speed up the output process to
the primary link. No action is necessary for this error type.


Have you busied and released the link.

Do a status on the data module.


Procedures for Restoring the CDR Link
1. Determine the status of CDR links.
Enter status cdr-link and make sure that the CDR links are not busied out for
maintenance. If the link is down, continue to the next step.
2. Where does the CDR link connect to?
Enter display system-parameters features and find out the destinations of CDR
links. Continue to the next step.
3. Enter status data extension and verify whether the data extension is in the in-service/
idle state. If the data extension is not available, look for the extension number in the Alt
Name field of the Error Log and see XXX-BD (Common Port Circuit Pack/Media
Module) on page 1407 for resolutions.
4. Is the external CDR output device available?
Make sure that the CDR output device is on-line and ready for service. Check the physical
connectivity between Data Module and the CDR output device.
5. If the problem is not found in the above steps, check the C-LAN board for any problems. For
description about system port and its connectivity, see CLAN-BD (Control LAN Circuit
Pack) on page 621.
When restoring the CDR link it is necessary to execute maintenance test on different objects
that comprise the CDR link. It is recommended that you busyout the CDR link before trying to
restore the link. When the CDR Link is busied out, then every CDR Link maintenance action is
deactivated, and interference to tests of other MOs is prevented.



[Started on Version 3 software 15 years a go]

 

[perchanski]

Hi, We have a site that has CDR via TCP/IP, it has never worked ever. Any chance u could cut and paste the CDR parameters, and all the the other stuff associated with it.
Cheers

 

[inerguard]

Copy the below for the CDR1 (ignore the SAT service):-

change ip-services Page 1 of 3

IP SERVICES
Service Enabled Local Local Remote Remote
Type Node Port Node Port
SAT y clan01b4 5024 any 0
CDR1 clan01a04 0 MDICallLogger 5101


Page 2 is left blank, page 3 as follows: -

change ip-services Page 3 of 3

SESSION LAYER TIMERS
Service Reliable Packet Resp Session Connect SPDU Connectivity
Type Protocol Timer Message Cntr Cntr Timer

CDR1 n 30 3 3 60




Set up a data module as follows: -


change data-module 2902 Page 1 of 1
DATA MODULE

Data Extension: 2902 Name: CLAN 01A0417
Type: ethernet
Port: 01A0417
Link: 3




Network uses 1's for Broadcast Addresses? y


Now change the sys parameters cdr as follows: -


change system-parameters cdr Page 1 of 2
CDR SYSTEM PARAMETERS

Node Number (Local PBX ID): 1 CDR Date Format: day/month
Primary Output Format: customized Primary Output Endpoint: CDR1
Secondary Output Format:
Use ISDN Layouts? n Enable CDR Storage on Disk? n
Use Enhanced Formats? n Condition Code 'T' For Redirected Calls? n
Use Legacy CDR Formats? y Remove # From Called Number? y
Modified Circuit ID Display? n Intra-switch CDR? y
Record Outgoing Calls Only? n Outg Trk Call Splitting? y
Suppress CDR for Ineffective Call Attempts? y Outg Attd Call Record? y
Disconnect Information in Place of FRL? n 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 Agent ID on Incoming? y Record Agent ID on Outgoing? y
Inc Trk Call Splitting? y Inc Attd Call Record? y
Record Non-Call-Assoc TSC? n Call Record Handling Option: warning
Record Call-Assoc TSC? n Digits to Record for Outgoing Calls: outpulsed
Privacy - Digits to Hide: 0 CDR Account Code Length: 15


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

Record length = 109

I think you also need to put the extensions you want to log in the following table (i don't have any, but you might need this): -


change intra-switch-cdr Page 1 of 3
INTRA-SWITCH CDR

Assigned Members: 0 of 5000 administered
Extension Extension Extension Extension




Try this lot which should help you out.









[Started on Version 3 software 15 years a go]

 

[perchanski]

thanks for that, excellent

 

[inerguard]

where's my star then, lolol.


[Started on Version 3 software 15 years a go]