vicidial.org

Newbie so please pardon me

I'm writing some reports off the back end of the asterisk database and I was looking at the vicidial_did_log table and wondering how come the uniqueid field is not set as the primary key on the table? Does anyone know if any version of vici has it set as the primary key?

Thanks in advance!

It is not set because the same call can be redirected to a different DID in the system, resulting in the same uniqueid for two different entries.

mflorell - thanks so much for the clarification!

But now I have a followup question - we have been using vici dialer for around 3 years now and have used and abused the system in most ways imaginable with the administration of the system changing hands multiple times between individuals of both high and low mental caliber While I can't categorically say that our system was setup to redirect calls to a different DID, we have about 280k records in that table and I have not seen a single instance of the uniqueid being duplicated. Is that possible under the scenario you mention? Understanding this is particularly important for us as we count all entries recorded in this table against any given DID as the total number of calls made to that DID, if this includes redirects as you mentioned, I'd like som help identifying those. Looking for duplicate uniqueids will not help in our situation as I mentioned since we have none.

On a related note re the original question, couldn't one use a combination of the uniqueid AND the call_date as a primary key?

Thanks again for all your assistance!

If you never configured it to do that then it wouldn't log in that way.

You can alter the database if you want, it would only cause a problem if you decided to route a DID to another DID.

Using a combination of uniqueid and call_date as unique still might be problematic since you can route a DID to another DID entry in less than one second.

Thanks again for the quick response. I will try to run some tests and see what I find and report back.