[OpenSIPS-Users] CDRTool - disable or minimize normalization

Jeff Pyle jpyle at fidelityvoice.com
Sat Mar 12 04:31:21 CET 2011


In case someone finds this later on with similar issues, I'll tell the rest of the story.

Setting the skipNormalize field to 1 or true in each data source did stop the normalization.  This stopped the problem of fields changing when I didn't want them too.  But, it also caused CDRTool to not display everything the same way as a normalized call.

For example, failed calls (486, 503, etc) displayed as "in progress".  I have other processes that add Rating info and Prices, and they weren't displayed anymore.  Neither was the KBIn or KBOut of a call tha went through a Mediaproxy relay.  Hmm.

I solved the issue by normalizing the calls in the stored procedures.  This really isn't the same "bringing them into a normal format" the normalizing procedure normally does, but rather only setting the flag to 1 once the call was complete.  I updated the insert_radacct_record procedure to set Normalized='1', unless SipResponseCode=200, in which case we'll set the field with the update_radacct_record.  I modified the update_radacct_record procedure to set Normalized='1' instead of the '0' it already had.

So, problem solved.  Of course maintaining these updates will require re-modifying the procedures each time the a new version of CDRTool requires updating the procedures in MySQL.  Definitely worth it, though.  CDRTool is still a fantastic utility when used only as a display front-end for the database.


- Jeff


From: Jeff Pyle <jpyle at fidelityvoice.com<mailto:jpyle at fidelityvoice.com>>
Reply-To: OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Date: Tue, 8 Mar 2011 12:28:27 -0500
To: OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Subject: Re: [OpenSIPS-Users] CDRTool - disable or minimize normalization

Yep, that did it.  Excellent.

From: Adrian Georgescu <ag at ag-projects.com<mailto:ag at ag-projects.com>>
Reply-To: OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Date: Tue, 8 Mar 2011 03:40:57 -0500
To: OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Subject: Re: [OpenSIPS-Users] CDRTool - disable or minimize normalization

Actually I found it, there is an undocumented variable skipNormalize:

Set skipNormalize to 1 or true in your data source to disable the normalization process.

Adrian

On Mar 8, 2011, at 3:32 AM, Jeff Pyle wrote:

Adrian,

I did as you said but it is still normalizing the data.  The top of cdr_generic.php now looks like this:

class CDRS {

    var $CDR_class           = 'CDR';
    var $intAccessCode       = '00';
    var $natAccessCode       = '0';
    var $maxrowsperpage      = 15;
    var $status              = array();
//    var $normalizedField     = 'Normalized';
    var $DestinationIdField  = 'DestinationId';
    var $BillingIdField      = 'UserName';

And there is no mention of normalizedField in /etc/cdrtool/global.inc.


- Jeff


From: Adrian Georgescu <ag at ag-projects.com<mailto:ag at ag-projects.com>>
Reply-To: OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Date: Wed, 2 Mar 2011 03:52:24 -0500
To: OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Subject: Re: [OpenSIPS-Users] CDRTool - disable or minimize normalization

You may comment out any definition of $normalizedField variable in cdr_generic.php and global.inc, without it the normalization process will not save anything in the database.

Adrian

On Mar 1, 2011, at 11:25 PM, Jeff Pyle wrote:

Hello,

Is there a simple way to disable normalization in CDRTool?  We use it only to view the CDRs, not do any billing or rating.  And the Normalization process is doing some strange things to some of the fields.

Or perhaps, if it must run, to minimize the impact it has?

Specifically, it is mangling international numbers, then reporting "No destination for number xxxxxxxx".  It changes some other fields that don't necessarily need to be changed, but less harmful.

I've played with the E164 field in global.inc for the data source but it doesn't seem to have any effect.


- Jeff
_______________________________________________
Users mailing list
Users at lists.opensips.org<mailto:Users at lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
Users at lists.opensips.org<mailto:Users at lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20110311/0d19ad58/attachment-0001.htm>


More information about the Users mailing list