Why not install 4.1.x and get raw CDR and inspect it? The ISO was taken down a few weeks ago it seems while they finalize some instability issues. I have a copy of the last ISO as I installed it on a lab system. If you need a copy, let me know.
-----Original Message----- From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Josh Patten Sent: Wednesday, February 03, 2010 12:09 PM To: Scott Lawrence Cc: sipx-users@list.sipfoundry.org Subject: Re: [sipx-users] New CDR database design There is no way from the generated CDR's to follow the call flow. There is also no way to know how long a call actually lasted if it was transferred or put on hold. This information exists in the Call State Events table but doesn't transfer over to the cdrs table. I posted about the ideas I had for CDR a few weeks ago and got told that I should look into a third party option. It just so happens my development team is in-between projects right now and are willing to meet with me to discuss writing something to parse this information out. I need raw data/models for 4.2 to give them so they can have something to work with. Josh Patten Assistant Network Administrator Brazos County IT Dept. (979) 361-4676 On 2/3/2010 1:59 PM, Scott Lawrence wrote: > On Wed, 2010-02-03 at 13:43 -0600, Josh Patten wrote: > >> I am curious what the new CDR database design is going to look >> like/consist of. I am meeting with my programming team today to discuss >> writing a CDR parser and I would like to show them examples of what kind >> of data they can expect to work with. As it currently stands it looks >> like they will have to parse Call State Events to get any useful >> information. I have figured out what most of the different data types >> mean and how they can be utilized to extract useful information. Will >> the Call State Events table remain relatively similar to it's current >> schema or are their major changes on the way for the entire CDR database? >> > The intent has been that the Call State Events are internal (and > therefor subject to change), and the CDRs are public. > > Can you give some examples of what you need that you can't get from the > resolved CDRs? > > > > > _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
