Duplicate Entries on vicidial_agent_log

[martinch]

Good afternoon team,

I'm seeing entries on the `vicidial_agent_log` table having multiple entries with the same `uniqueid` in them.

The consequence of this is we're seeing essentially two or more rows with a supposedly linked to a single call.

Anybody else ever seen this behavior in vicidial?

Thanks in advance,

Martin

[williamconley]

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method (7.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... BUILD: #####-####).

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) uniqueid is the name of the value in asterisk. It's NOT a unique field in mysql, nor is it actually a unique value at all. Just what they named a value. If you want to "identify a call" use another field or a combination of fields intead.

Welcome to Open Source, my friend!

[ambiorixg12]

Based on the documentation

uniqueid Identifier for phone call, generated by Asterisk at the onset of call

For me seems to be weirds more than 1 rows with the same ID if is not the same call, unless all the rows are related to a single call because the uniqueid Asterisk identifier for a channel

[williamconley]

Based on the documentation

uniqueid Identifier for phone call, generated by Asterisk at the onset of call

For me seems to be weirds more than 1 rows with the same ID if is not the same call, unless all the rows are related to a single call because the uniqueid Asterisk identifier for a channel

You do know that Linux, Asterisk and Vicidial are all Open Source? LOL

That being said: Your post shows "uniqueid" and "identifier" right next to each other. One is the "item being defined" and the other is the "definition". Thus "uniqueid" is defined as an "identifier" ... but NOT a "unique" identifier. I'd like to explain it deeper, but it's been a while. I can, however, tell you from experience that it is NOT unique and that is why the table in question does NOT use this field as the primary key (which would enforce its uniqueness). Also consider the most obvious that multiple server installations could easily have the same id in that location since it's not random and not long enough to be guaranteed unique (time-based is never unique, right?)

[ambiorixg12]

OK, if is not unique identifier is good to know it. Vicidial has a tons of tables and is hard to determine what it is the purposes of each one if you don't have a documentation or you start hunting your self. I guess last option is more funy lol

[williamconley]

If you are seeking the use for any log: use grep on the command line in the /usr/share/astguiclient, /var/lib/asterisk/agi-bin, and /srv/www/htdocs/vicidial (/agc) folders to search for the name of the table (case insensitive). Each table will have at least one script that writes to it during a call and most will have at least one place that reads it for at least one report. Often just the filenames of the scripts will give you a hint as to the purpose of the table.

[ambiorixg12]

If you are seeking the use for any log: use grep on the command line in the /usr/share/astguiclient, /var/lib/asterisk/agi-bin, and /srv/www/htdocs/vicidial (/agc) folders to search for the name of the table (case insensitive). Each table will have at least one script that writes to it during a call and most will have at least one place that reads it for at least one report. Often just the filenames of the scripts will give you a hint as to the purpose of the table.

Interesting information, thanks