[Asterisk-Users] 1.2beta and PRI and CDR Corruption

Matthew Boehm mboehm at cytelcom.com
Wed Aug 31 11:06:30 MST 2005


Anyone out there running 1.2beta with a PRI and having CDR problems?

I just upgraded to most recent everything and now my CDR's look like this:

"","▒▒▒▒","9035646130","copper_routing","▒▒▒▒","Zap/65-1","SIP/netl-a3ac","Dial","SIP/+19035646130 at netl|60","2005-08-31 
13:03:09","2005-08-31 13:03:20", "2005-08-31 
13:03:29",20,9,"ANSWERED","DOCUMENTATION"

That is a direct text copy/paste from Master.csv

This only seems to affect incomming PRI calls. All other calls (inc SIP, 
out SIP, out PRI) show correct CDRs.

I'm worried this corruption of data may eventualty lead to a crash but 
so far nothing.

CallerIDName is parsed correctly:

"","▒▒▒▒p^","8322008630","macro-faxrecordvoicemail","""BOEHM MATTHEW  "" 
<▒▒▒▒p^>","Zap/2-1","SIP/3044-b976","Dial","SIP/3044|10|wt","2005-08-31 
13:06:36","2005-08-31 13:06:36","2005-08-31 
13:06:42",6,6,"ANSWERED","DOCUMENTATION"

but CallerIDNumber is not; as evidenced above.

Any thoughts? Ideas? Should I be reverting asterisk code backwards or 
libpri?

-Matthew




More information about the asterisk-users mailing list