[Freeswitch-users] Duplicate CDRs

David Ponzone david.ponzone at ipeva.fr
Fri Oct 1 09:08:23 PDT 2010 

Steven,

I confirm the default is log B-leg:

     <!-- optional: if not present we do log the b leg -->

David Ponzone  Direction Technique
email: david.ponzone at ipeva.fr
tel:      01 74 03 18 97
gsm:   06 66 98 76 34

Service Client IPeva
tel:      0811 46 26 26
www.ipeva.fr  -   www.ipeva-studio.com

Ce message et toutes les pièces jointes sont confidentiels et établis  
à l'intention exclusive de ses destinataires. Toute utilisation ou  
diffusion non autorisée est interdite. Tout message électronique est  
susceptible d'altération. IPeva décline toute responsabilité au titre  
de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes  
pas destinataire de ce message, merci de le détruire immédiatement et  
d'avertir l'expéditeur.




Le 01/10/2010 à 17:45, Steven Ayre a écrit :

> Are they A and B leg CDRs? For a bridged call you'll see a CDR for
> both the A and B leg, which as separate channels will each have its
> own UUID but will share the same caller id, destination number and
> call duration.
>
> <!--param name="log-b-leg" value="false"/-->
> That parameter would disable logging the B-leg CDRs. You have it
> commented out. I can't remember the default setting but from what you
> describe, default behaviour might be to log both.
>
> Look at the Direction that is submitted to tell the difference between
> A and B legs. It'll either be inbound (A) or outbound (B). You could
> then ignore B-legs in your PHP script, or handle them differently.
>
> -Steve
>
>
> On 1 October 2010 11:17, Saeed Ahmed <saeedahmad1981 at gmail.com> wrote:
>> Dear List,
>>
>> I am using xml_cdr to write the records on disk.
>>
>> today for first time when there was a call pressure around 60-70  
>> concurrent
>> calls (around 140 session), then FS started to write same CDR  
>> record two
>> times with different/unique file name and also different/unique  
>> UUIDs etc..
>> but the called number, start time, end time everything is same. so  
>> its
>> surely a duplicated CDR.
>>
>> -> I am running FS on cent os, on a 6 core machine with 4  GM RAM.
>> -> FS version: FreeSWITCH Version 1.0.head (git-72baaf6 2010-09-21  
>> 19-22-28
>> -0500) (is anything regarding cdr changed in new version? so i can  
>> upgrade)
>>
>>> Please note that system was running fine with few call attempts  
>>> and i
>>> never faced this prob, only in case of 6-70 councurrent calls
>>
>> My xml_cr.conf:
>>
>> <configuration name="xml_cdr.conf" description="XML CDR CURL logger">
>>   <settings>
>>     <!-- the url to post to if blank web posting is disabled  -->
>>     <!-- <param name="url" value="http://localhost/cdr_curl/ 
>> post.php"/> -->
>>
>>     <!-- optional: credentials to send to web server -->
>>     <!--    <param name="cred" value="user:pass"/> -->
>>
>>     <!-- the total number of retries (not counting the first 'try')  
>> to post
>> to webserver incase of failure -->
>>     <param name="retries" value="2"/>
>>
>>     <!-- delay between retries in seconds, default is 5 seconds -->
>>     <!-- <param name="delay" value="1"/> -->
>>
>>     <!-- Log via http and on disk, default is false -->
>>     <!-- <param name="log-http-and-disk" value="true"/> -->
>>
>>     <!-- optional: if not present we do not log every record to  
>> disk -->
>>     <!-- either an absolute path, a relative path assuming $ 
>> {prefix}/logs or
>> a blank value will default to ${prefix}/logs/xml_cdr -->
>>     <param name="log-dir" value="/opt/fscdr"/>
>>
>>     <!-- optional: if not present we do log the b leg -->
>>     <!-- true or false if we should create a cdr for the b leg of a  
>> call-->
>>     <!--param name="log-b-leg" value="false"/-->
>>
>>     <!-- optional: if not present, all filenames are the uuid of  
>> the call
>> -->
>>     <!-- true or false if a leg files are prefixed "a_" -->
>>     <param name="prefix-a-leg" value="true"/>
>>
>>     <!-- encode the post data may be 'true' for url encoding,  
>> 'false' for no
>> encoding or 'base64' for base64 encoding -->
>>     <param name="encode" value="true"/>
>>
>>     <!-- optional: set to true to disable Expect: 100-continue  
>> lighttpd
>> requires this setting -->
>>     <!--<param name="disable-100-continue" value="true"/>-->
>>
>>     <!-- optional: full path to the error log dir for failed web  
>> posts if
>> not specified its the same as log-dir -->
>>     <!-- either an absolute path, a relative path assuming $ 
>> {prefix}/logs or
>> a blank or omitted value will default to ${prefix}/logs/xml_cdr -->
>>     <param name="err-log-dir" value="/opt/error_cdr"/>
>>
>>     <!-- which auhtentification scheme to use. Supported values  
>> are: basic,
>> digest, NTLM, GSS-NEGOTIATE or "any" for automatic detection -->
>>     <!--<param name="auth-scheme" value="basic"/>-->
>>
>>     <!-- optional: this will enable the CA root certificate check  
>> by libcurl
>> to
>>          verify that the certificate was issued by a major  
>> Certificate
>> Authority.
>>          note: default value is disabled. only enable if you want  
>> this! -->
>>     <!--<param name="enable-cacert-check" value="true"/>-->
>>     <!-- optional: verify that the server is actually the one  
>> listed in the
>> cert -->
>>     <!-- <param name="enable-ssl-verifyhost" value="true"/> -->
>>
>>     <!-- optional: these options can be used to specify custom SSL
>> certificates
>>          to use for HTTPS communications. Either use both options or
>> neither.
>>          Specify your public key with 'ssl-cert-path' and the  
>> private key
>> with
>>          'ssl-key-path'. If your private key has a password,  
>> specify it with
>>          'ssl-key-password'. -->
>>     <!-- <param name="ssl-cert-path"
>> value="$${base_dir}/conf/certs/public_key.pem"/> -->
>>     <!-- <param name="ssl-key-path"
>> value="$${base_dir}/conf/certs/private_key.pem"/> -->
>>     <!-- <param name="ssl-key-password"  
>> value="MyPrivateKeyPassword"/> -->
>>
>>     <!-- optional: use a custom CA certificate in PEM format to  
>> verify the
>> peer
>>          with. This is useful if you are acting as your own  
>> certificate
>> authority.
>>          note: only makes sense if used in combination with
>> "enable-cacert-check." -->
>>     <!-- <param name="ssl-cacert-file"
>> value="$${base_dir}/conf/certs/cacert.pem"/> -->
>>
>>     <!-- optional: specify the SSL version to force HTTPS to use.  
>> Valid
>> options are
>>          "SSLv3" and "TLSv1". Otherwise libcurl will auto-negotiate  
>> the
>> version. -->
>>     <!-- <param name="ssl-version" value="TLSv1"/> -->
>>
>>     <!-- optional: enables cookies and stores them in the specified  
>> file.
>> -->
>>     <!-- <param name="cookie-file" value="/tmp/cookie- 
>> mod_xml_curl.txt"/>
>> -->
>>   </settings>
>> </configuration>
>>
>>
>> Many Thanks
>> - Saeed
>>
>> _______________________________________________
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org
>>
>>
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20101001/788ec642/attachment.html

More information about the FreeSWITCH-users mailing list