[Spce-user] Outgoing CDR Records

[Kevin Masse]

I agree that is most certainly the reason this happened.  


I am having one problem.  When I run the command you will see near the
bottom that after clearing it and making a call it comes back again.

First I had a couple of accounts with the issue but now as soon as I
make a call the service pops up another issue with the same warnings.

Within 5 seconds of making an outbound call we go back to another error.
Perhaps it is wider spread than just the one account, although the same
account keeps coming up.


rollback ineffective with AutoCommit enabled at /usr/sbin/rate-o-mat
line 91.
rollback ineffective with AutoCommit enabled at /usr/sbin/rate-o-mat
line 92.
Error rating CDR batch: No reseller info for user id
7f7c19f9-92d2-432b-a845-fbeea01727a8 found



mysql> update cdr set rating_status = 'ok' where source_user_id =
'ded1ec90-b3e1-4346-a38d-b89d83c1547f';
Query OK, 3 rows affected (0.05 sec)
Rows matched: 15  Changed: 3  Warnings: 0

mysql> update cdr set rating_status = 'ok' where source_user_id =
'4efc4248-44e4-403d-887b-2402b4410a04';
Query OK, 124 rows affected (0.11 sec)
Rows matched: 124  Changed: 124  Warnings: 0

mysql> update cdr set rating_status = 'ok' where source_user_id =
'7f7c19f9-92d2-432b-a845-fbeea01727a8';
Query OK, 1 row affected (0.00 sec)
Rows matched: 19  Changed: 1  Warnings: 0

mysql> update cdr set rating_status = 'ok' where source_user_id =
'7f7c19f9-92d2-432b-a845-fbeea01727a8';
Query OK, 1 row affected (0.00 sec)
Rows matched: 20  Changed: 1  Warnings: 0

mysql> update cdr set rating_status = 'ok' where source_user_id =
'7f7c19f9-92d2-432b-a845-fbeea01727a8';
Query OK, 1 row affected (0.00 sec)
Rows matched: 22  Changed: 1  Warnings: 0

mysql> update cdr set rating_status = 'ok' where source_user_id =
'7f7c19f9-92d2-432b-a845-fbeea01727a8';
Query OK, 1 row affected (0.00 sec)
Rows matched: 23  Changed: 1  Warnings: 0



Thank you
Kevin




-----Original Message-----
From: Andreas Granig [mailto:agranig at sipwise.com] 
Sent: Friday, February 08, 2013 4:22 PM
To: Kevin Masse
Cc: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Outgoing CDR Records

Hi,

Looks like you deleted the subscriber via SOAP or XMLRPC before the
rating process went over its CDRs. There is a SOAP function called
something like terminate_subscriber (don't know it by heart, please
check the WSDL) which the admin panel uses (instead of
delete_subscriber) when you "delete" a subscriber to prevent exactly
this issue. Only really delete subscribers if you're sure their CDRs got
rated, so the safe way is to terminate them, wait for a grace period
(e.g. couple of days or at least until you're 100% sure the CDRs of the
subscribers got rated), then finally delete them.

The only way to get your rating up-and-running again now is to update
the accounting.cdr table manually by setting the rating_status to "ok" 
for source_subscriber_id=7f7c19f9-92d2-432b-a845-fbeea01727a8.

Andreas

On 02/08/2013 10:01 PM, Kevin Masse wrote:
> Thank you for the reply, the UUID 7f7c19f9-92d2-432b-a845-fbeea01727a8
> does not exist.
>
> I cannot locate a contract id because the UUID is not in the database.
> I searched via the Web Admin portal and right out of the database 
> exactly where you stated to look.
>
>
> Could it be a stale record in the database in an additional location?
>
> Regards,
> Kevin
>
>
>
> -----Original Message-----
> From: Andreas Granig [mailto:agranig at sipwise.com]
> Sent: Friday, February 08, 2013 3:27 PM
> To: Kevin Masse
> Cc: spce-user at lists.sipwise.com
> Subject: Re: [Spce-user] Outgoing CDR Records
>
> Hi,
>
> On 02/08/2013 07:42 PM, Kevin Masse wrote:
>> Andreas I have provided the following based on your request.
> Additionally I did not manually edit any of the database files.
>>
>> mysql> select * FROM contracts where
>> mysql> id='7f7c19f9-92d2-432b-a845-fbeea01727a8'\G
>
> This is not the contract id, it's the uuid of the subscriber. You can 
> find the contract id for this uuid in the account_id column of 
> provisioning.voip_subscribers (or more easily in the web admin panel).
>
> Andreas
>