trunk access code in cdr 1

[tucker3]

after upgrading from Release 24 to succession 5.0, cdr records are showing the trunk access code instead of the bars access code. how can we change it to the bars access code?

 

[GHTROUT]

The LD17 FCDR prompt might be worth toggling

GHTROUT.com | FAQs | Recent Replies

 

[pronei]

Hold on a sec!!

Changing CDR type from OLD <-> NEW could result in malformed MDR CDR Collection and Call Accounting Application Data.

First,

1. Are you using the data for Call Accounting purposes?
2. Are you collection your RAW data to an MDR2000, Direct Serial or IP?
3. Are you in a position to experiment with CDR or is it vital to your organization?

If your using an MDR2000, before you make changes to the CDR data type, you need to modify the settings in the MDR2000.

 

[tucker3]

we are using a direct serial connection to a 3rd part app supported by someone else. The old data sent used to be the bars access code followed by the number dialed. now we are sending the trunk access code followed by number dialed. there software is only set to delete 1 digit so now it is billing local calls. We can play with it for today. We have tried the FCDR promt it just adds an A in front of the access code in the raw data.

 

[pronei]

I've tried several modifications on my CDR stream today, I could not get AC1 to display in place of the Route ACOD in any scenario.

That may not be possible anymore. I've never seen AC1 in CDR in any of the switches I've worked on. Always been Route's ACOD.

Quickest fix would most likely be to call the call accounting vendor and have them adjust to new CDR data stream.