Hi,
I'm having some challenges with Siremis, and it says on the project website that this list is the place to ask - so here are the two issues:
1. Repeats: I had problems with repeats in the cdrs table. This was possible, because I had forgotten to set the correct unique index (call_id + from_tag + to_tag). Once this was set, it was obviously not possible to make the repeats anymore - so problem solved. But I still wonder: why was it trying to calculate calls that had already been calculated? Shouldn't it ignore these and only treat new ones?
2. Missing calcs After an unsuccessful attempt to upgrade MySql from 5.0 to 5.1, it seems that not all calls are being calculated and put in the cdrs table. The CRON job was stopped due to the failed upgrade of MySql, but I started it again later - MySql was not down. However, I thought it would 'catch up' with the transaction that had not been calculated while the CRON job for the stored procedure had been off, but it did not. In fact, it seems that not all calls are being calculated and put inthe cdrs table - I'm missing almost half the calls. Any idea what this can be?
Thanks!!
//Anders
#2 of the issues below I "solved" - I restarted the box, and it caught up on the back-lag and is calculating everything right. I have no clue why, - but it works.
The first one I still wonder about, so if any SIREMIS gurus have input, I'm all ears...
//Anders
On Wed, May 19, 2010 at 11:30 AM, Anders vaerge@gmail.com wrote:
Hi,
I'm having some challenges with Siremis, and it says on the project website that this list is the place to ask - so here are the two issues:
- Repeats:
I had problems with repeats in the cdrs table. This was possible, because I had forgotten to set the correct unique index (call_id + from_tag + to_tag). Once this was set, it was obviously not possible to make the repeats anymore - so problem solved. But I still wonder: why was it trying to calculate calls that had already been calculated? Shouldn't it ignore these and only treat new ones?
- Missing calcs
After an unsuccessful attempt to upgrade MySql from 5.0 to 5.1, it seems that not all calls are being calculated and put in the cdrs table. The CRON job was stopped due to the failed upgrade of MySql, but I started it again later - MySql was not down. However, I thought it would 'catch up' with the transaction that had not been calculated while the CRON job for the stored procedure had been off, but it did not. In fact, it seems that not all calls are being calculated and put inthe cdrs table - I'm missing almost half the calls. Any idea what this can be?
Thanks!!
//Anders
-
Anders