[Spce-user] Database Question (CDRs) v2.6
Kevin Masse
kmasse at questblue.com
Thu Apr 4 13:43:35 EDT 2013
Thank you for the valuable input Mario, currently it is on a dedicated system and our programmers have just reworked what we pull for records making sure we have (distinct(start_time)) and this allowed us to move forward without the duplicates.
I will still check the speed of the disks on this installation to be sure they are the fastest for the server that can be installed to make sure we have proper seek and write time.
Thank you,
Kevin
-----Original Message-----
From: Mario Contreras [mailto:mario.contreras at innovasur.es]
Sent: Thursday, April 04, 2013 1:32 PM
To: Kevin Masse
Cc: Spce-user at lists.sipwise.com; Aníbal Cañada
Subject: Re: [Spce-user] Database Question (CDRs) v2.6
Hi Kevin,
I had a problem related with disk latency. Kamailio wasn't able to attend the amount of petitions subscribers did. So, it can produce duplicate byes, like Anibal says. You can look up the dastastore latency if you use vmware. I hope it's useful to you.
Regards,
Mario
El jueves, 04 de abril de 2013 16:40:07, Kevin Masse escribió:
> Aníbal that would be excellent as a temporary solution for me is you
> wouldn’t mind sharing the scripts. I could really use that step in
> the right direction today to at least have accurate records.
>
> Additionally thank you for sharing the details of what you discovered.
>
> Regards,
>
> Kevin
>
> *From:*Aníbal Cañada [mailto:anibal at hercom.es]
> *Sent:* Thursday, April 04, 2013 10:36 AM
> *To:* Kevin Masse
> *Cc:* <Spce-user at lists.sipwise.com>
> *Subject:* Re: [Spce-user] Database Question (CDRs) v2.6
>
> I can send you the cleans scripts , if you wanna a base or other
> approach to that solution.
>
> About the dupplicated CDR we activate the mysql log in my.cnf and the
> problem came from mediator.
>
> In the kamailio db, when mediator pass from the kamailio acc to the
> CDR db,
>
> If it find an invite line but two bye from the same call,he
> dupplicated the call in the CDR.
>
> Our final conclusión was speed disk problems, but we cant optimize the
> mysql for that and go for the bare metal solution.
>
> Anyway, i still have the machine with the dupplicated CDR if you wanna
> try or compare something
>
> Anibal cañada
>
>
> El 04/04/2013, a las 15:54, "Kevin Masse" <kmasse at questblue.com
> <mailto:kmasse at questblue.com>> escribió:
>
> Thank you for the response Aníbal, I was thinking about scrubbing
> the CDR’s also just as you have done in the past.
>
>
> We are on a dedicated quad Xeon with 32G ram for the Sipwise
> installation and it is still happening.
>
> I also understand that we are now a couple of revisions behind as
> we are on 2.6 but we have not completed our testing of upgrading yet.
>
> Thank you again for your quick reply and information. Outside of
> us scrubbing the CDR’s when we find the issue we can post it for
> all to review.
>
> Regards,
>
> Kevin
>
> *From:*Aníbal Cañada [mailto:anibal at hercom.es]
> *Sent:* Thursday, April 04, 2013 9:40 AM
> *To:* Kevin Masse
> *Cc:* <Spce-user at lists.sipwise.com
> <mailto:Spce-user at lists.sipwise.com>>
> *Subject:* Re: [Spce-user] Database Question (CDRs) v2.6
>
> Hi,
>
> We had this issue with a virtualized Sipwise.
>
> I have a script for clean the database but was a dirty and
> temporal solution.
>
> The unique solution we found was install in bare metal machine.
>
> We installing Sipwise in a Dell r420 and all the problems had gone.
>
> Sorry for my bad english , i am writting from my phone.
>
> Anibal cañada
>
>
> El 04/04/2013, a las 15:15, "Kevin Masse" <kmasse at questblue.com
> <mailto:kmasse at questblue.com>> escribió:
>
> Hello, I would like to see if there are any other users that
> have seen duplicate call records in the CDRs (accounting.cdr)
>
> We are attempting to pull the CDRs based on ID and we are
> seeing duplicated data in the report. At first we thought it
> could have something to do with our query but when I login to
> MySQL on Sipwise I see the duplicates are there so the data we
> are pulling is valid.
>
> 224836
>
>
>
> #########
>
>
>
> 1#########
>
>
>
> ok
>
>
>
> 200
>
>
>
> 4/3/2013 8:59
>
>
>
> 4/3/2013 8:59
>
>
>
> 1254.35
>
> 224837
>
>
>
> #########
>
>
>
> 1#########
>
>
>
> ok
>
>
>
> 200
>
>
>
> 4/3/2013 8:59
>
>
>
> 4/3/2013 8:59
>
>
>
> 1254.35
>
> 224838
>
>
>
> #########
>
>
>
> 1#########
>
>
>
> ok
>
>
>
> 200
>
>
>
> 4/3/2013 8:59
>
>
>
> 4/3/2013 8:59
>
>
>
> 1254.35
>
> The above information is coming from our report externally but
> I used the query below to verify the records match:
>
> mysql> select * from cdr where source_account_id=115 or
> destination_account_id=115 \G
>
> As I thought, the records we are pulling are accurate but the
> client did have 3 calls at the very same time for the exact
> amount of seconds in reality. Additionally, there are
> numerous duplications on the clients CDR’s but not all of them.
>
> *************************** 56. row
> ***************************
>
> id: 224836
>
> update_time: 2013-04-03 09:20:17
>
> source_user_id:
> daf5bfbe-731f-4f0c-b490-598b45bac427
>
> source_provider_id: 1
>
> source_external_subscriber_id:
>
> source_external_contract_id:
>
> source_account_id: 115
>
> source_user: ##########
>
> source_domain: ##.##.##.##
>
> source_cli: ##########
>
> source_clir: 0
>
> source_ip: ##.##.##.##
>
> destination_user_id: 0
>
> destination_provider_id: 3
>
> destination_external_subscriber_id:
>
> destination_external_contract_id:
>
> destination_account_id: 0
>
> destination_user: 1##########
>
> destination_domain: ##.##.##.##
>
> destination_user_dialed: 1##########
>
> destination_user_in: 1##########
>
> destination_domain_in: ##.##.##.##
>
> peer_auth_user:
>
> peer_auth_realm:
>
> call_type: call
>
> call_status: ok
>
> call_code: 200
>
> init_time: 1364993954.737
>
> start_time: 1364993958.260
>
> duration: 1254.350
>
> call_id:
> 098f8fb12a0313c11f2d940c37f0cd14@##.##.##.##:5060
> <mailto:098f8fb12a0313c11f2d940c37f0cd14@##.##.##.##:5060>
>
> carrier_cost: 0.00
>
> reseller_cost: 0.00
>
> customer_cost: 0.00
>
> carrier_free_time: NULL
>
> reseller_free_time: NULL
>
> customer_free_time: NULL
>
> carrier_billing_fee_id: NULL
>
> reseller_billing_fee_id: NULL
>
> customer_billing_fee_id: NULL
>
> carrier_billing_zone_id: NULL
>
> reseller_billing_zone_id: NULL
>
> customer_billing_zone_id: NULL
>
> frag_carrier_onpeak: NULL
>
> frag_reseller_onpeak: NULL
>
> frag_customer_onpeak: NULL
>
> is_fragmented: NULL
>
> split: 0
>
> rated_at: NULL
>
> rating_status: unrated
>
> exported_at: NULL
>
> export_status: unexported
>
> *************************** 57. row
> ***************************
>
> id: 224837
>
> update_time: 2013-04-03 09:20:17
>
> source_user_id:
> daf5bfbe-731f-4f0c-b490-598b45bac427
>
> source_provider_id: 1
>
> source_external_subscriber_id:
>
> source_external_contract_id:
>
> source_account_id: 115
>
> source_user: ##########
>
> source_domain: ##.##.##.##
>
> source_cli: ##.##.##.##
>
> source_clir: 0
>
> source_ip: ##.##.##.##
>
> destination_user_id: 0
>
> destination_provider_id: 3
>
> destination_external_subscriber_id:
>
> destination_external_contract_id:
>
> destination_account_id: 0
>
> destination_user: 1##########
>
> destination_domain: ##.##.##.##
>
> destination_user_dialed: 1##########
>
> destination_user_in: 1##########
>
> destination_domain_in: ##.##.##.##
>
> peer_auth_user:
>
> peer_auth_realm:
>
> call_type: call
>
> call_status: ok
>
> call_code: 200
>
> init_time: 1364993954.737
>
> start_time: 1364993958.260
>
> duration: 1254.350
>
> call_id:
> 098f8fb12a0313c11f2d940c37f0cd14@##.##.##.##:5060
> <mailto:098f8fb12a0313c11f2d940c37f0cd14@##.##.##.##:5060>
>
> carrier_cost: 0.00
>
> reseller_cost: 0.00
>
> customer_cost: 0.00
>
> carrier_free_time: NULL
>
> reseller_free_time: NULL
>
> customer_free_time: NULL
>
> carrier_billing_fee_id: NULL
>
> reseller_billing_fee_id: NULL
>
> customer_billing_fee_id: NULL
>
> carrier_billing_zone_id: NULL
>
> reseller_billing_zone_id: NULL
>
> customer_billing_zone_id: NULL
>
> frag_carrier_onpeak: NULL
>
> frag_reseller_onpeak: NULL
>
> frag_customer_onpeak: NULL
>
> is_fragmented: NULL
>
> split: 0
>
> rated_at: NULL
>
> rating_status: unrated
>
> exported_at: NULL
>
> export_status: unexported
>
> *************************** 58. row
> ***************************
>
> id: 224838
>
> update_time: 2013-04-03 09:20:17
>
> source_user_id:
> daf5bfbe-731f-4f0c-b490-598b45bac427
>
> source_provider_id: 1
>
> source_external_subscriber_id:
>
> source_external_contract_id:
>
> source_account_id: 115
>
> source_user: ##########
>
> source_domain: ##.##.##.##
>
> source_cli: ##########
>
> source_clir: 0
>
> source_ip: ##.##.##.##
>
> destination_user_id: 0
>
> destination_provider_id: 3
>
> destination_external_subscriber_id:
>
> destination_external_contract_id:
>
> destination_account_id: 0
>
> destination_user: 1##########
>
> destination_domain: ##.##.##.##
>
> destination_user_dialed: 1##########
>
> destination_user_in: 1##########
>
> destination_domain_in: ##.##.##.##
>
> peer_auth_user:
>
> peer_auth_realm:
>
> call_type: call
>
> call_status: ok
>
> call_code: 200
>
> init_time: 1364993954.737
>
> start_time: 1364993958.260
>
> duration: 1254.350
>
> call_id:
> 098f8fb12a0313c11f2d940c37f0cd14@##.##.##.##:5060
> <mailto:098f8fb12a0313c11f2d940c37f0cd14@##.##.##.##:5060>
>
> carrier_cost: 0.00
>
> reseller_cost: 0.00
>
> customer_cost: 0.00
>
> carrier_free_time: NULL
>
> reseller_free_time: NULL
>
> customer_free_time: NULL
>
> carrier_billing_fee_id: NULL
>
> reseller_billing_fee_id: NULL
>
> customer_billing_fee_id: NULL
>
> carrier_billing_zone_id: NULL
>
> reseller_billing_zone_id: NULL
>
> customer_billing_zone_id: NULL
>
> frag_carrier_onpeak: NULL
>
> frag_reseller_onpeak: NULL
>
> frag_customer_onpeak: NULL
>
> is_fragmented: NULL
>
> split: 0
>
> rated_at: NULL
>
> rating_status: unrated
>
> exported_at: NULL
>
> export_status: unexported
>
> What could cause the data for the call to duplicate?
>
> Thank you
>
> Kevin
>
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
> http://lists.sipwise.com/listinfo/spce-user
>
More information about the Spce-user
mailing list