Jump to content

< Back to Forum


Unknown Log Data

  • Please log in to reply

#1 Maciej 26 October 2015 - 06:49 PM


in log file we found something like this:


000000.344  12               ex    cmd_CoreSql.CommandText=INSERT into stats_ivr_call (port, datetime_start, datetime_end, calls_in_count, calls_in_time_seconds, calls_in_time_average, calls_out_count, calls_out_time_seconds, calls_out_time_average) VALUES (1, '2015-10-25T23:30:00', '2015-10-26T00:00:00', 0, 0, 0, 0, 0, 0);
000000.344  12               db    PerformWork_RunCoreSql ExecuteNonQuery call: INSERT into stats_ivr_call (port, datetime_start, datetime_end, calls_in_count, calls_in_time_seconds, calls_in_time_average, calls_out_count, calls_out_time_seconds, calls_out_time_average) VALUES (2, '2015-10-25T23:30:00', '2015-10-26T00:00:00', 0, 0, 0, 0, 0, 0);
000000.347  12         ERROR v7.5.5669.23446 (10-Jul-15 12:01:32.48) DbProcessQueue_DoQueuedWork_RunCoreSql : ERROR: 42P01: relation "stats_ivr_call" does not exist

   at Npgsql.NpgsqlState.<ProcessBackendResponses_Ver_3>d__a.MoveNext()
   at Npgsql.ForwardsOnlyDataReader.GetNextResponseObject()
   at Npgsql.ForwardsOnlyDataReader.GetNextRowDescription()
   at Npgsql.ForwardsOnlyDataReader.NextResult()
   at Npgsql.ForwardsOnlyDataReader..ctor(IEnumerable`1 dataEnumeration, CommandBehavior behavior, NpgsqlCommand command, NotificationThreadBlock threadBlock, Boolean synchOnReadError)
   at Npgsql.NpgsqlCommand.GetReader(CommandBehavior cb)
   at Npgsql.NpgsqlCommand.ExecuteNonQuery()
   at ktlib.vgDb.vgDb_ProviderInvariant.DbProcessQueue_DoQueuedWork_RunCoreSql(Object sender, ProcessingQueueEventArgs`1 args)


Do You know what it is?

#2 SupportTeam 26 October 2015 - 08:18 PM

VoiceGuide v7.5 saves periodic (30 min interval) usage statistics into the stats_ivr_call table.


If that table is not present you will see error messages like the one displayed. And looks like on your system that table is not there as you have set up system to use your own database (npgsql based)


Not having stats_ivr_call table does not affect handling of calls, but the historical usage statistics will not work.


Please see VoiceGuide v7.5's \system\setup\DB_Create_System.Data.SQLite.sql for stats_ivr_call table (and others) schema/structure.


Adding this table to your custom NpgSQL database will stop these error messages from appearing in the trace logs.

#3 SupportTeam 26 October 2015 - 08:23 PM

Once you have the stats_ivr_call table set up, restart VoiceGuide and view this in any browser:




(or http://localhost:714..._ivr_basic.html )


or to view dashboard from remote computer use this:




also see: http://www.voiceguid...tingrestapi.htm

#4 Maciej 06 June 2016 - 05:30 PM

How to set up custom NpgSQL database?

I created table and now how to connect vg to this table?

#5 SupportTeam 06 June 2016 - 07:05 PM

If the stats_ivr_call table is set up then it will be automatically written to.


Previous posts in this thread show the INSERT attempts being made.



Instructions on how to set VoiceGuide to use a user-selected database for keeping system information is provided here:




But looks like that has already been set up on your system.

#6 Maciej 07 June 2016 - 08:51 PM

Thanks ...

#7 Maciej 07 June 2016 - 09:15 PM

Question is: we have seeral servers and how to identify in stats_ivr_call each one device?

I see stats but with multiply data from several servers without any individual ID.

#8 SupportTeam 07 June 2016 - 11:53 PM

Are you currently using a single OutDial/System database for several VoiceGuide servers?


VoiceGuide's own backend database that stores the outgoing calls / CDRs / statistics etc. should not be shared across multiple VoiceGuide servers. That is not an officially supported configuration. Each VoiceGuide instance assumes that the database from which it reads new outgoing calls etc is set up for that server instance only, and not shared across multiple servers.


If you are using a single database, then how are you differentiating the CDR records saved there from multiple servers? Or do you just use the file based CDR records from individual servers?

#9 SupportTeam 08 June 2016 - 10:07 AM

Do you have a requirement to see all call statistics in one place?


The web based dashboards that come with VoiceGuide use the REST API calls to VoiceGuide server to retrieve call data from that particular server.

The dashboards are easily modified to retrieve data from multiple servers - just add more 'Datasources' - which each datasource retrieving data from REST API of a different server.

So it is easy to set up the VoiceGuide dashboard to show call data from multiple VoiceGuide servers on same dashboard.


If your requirement is to have all info in one database table then saving statistical data from multiple servers into one central database would be a straightforward modification within VoiceGuide.

We could even extend that to allow other VoiceGuide generated data data (eg. CDRs) to be saved to separate user-settable databases as well.

If you can outline what your requirements are we could have a look at how to best meet them.