Jump to content


< Back to Forum


 

Queid Was Updated With -1 Value In Calltrack Table


  • Please log in to reply

#1 ID2016 14 March 2017 - 02:36 AM

After conversion from Vg6 to Vg7 voip when I ran the same vgs script, the queid was updated with -1 value in calltrack table and no script playing when phone rings.

 

I resinstalled sql stored procedure for the database as it was requested above and it fixed the table creation issue. But now there is a different problem.

 

Please check the logs.



#2 SupportTeam 14 March 2017 - 07:31 PM

The -1 in calltrack's "queid" field is probably related to the disabling of the "porttouse" table on this system by setting zConfigXml_sDialer_OutDialQue_porttouse_LinkField entry to Disable in the Config.xml

 

This disables ability to select the specific port(s) on which the loaded outgoing call can be made out on, and looks like disabling this affected the calltrack table as well.

 

In the version you have on system right now the "PortToUse_LinkField" in Config.xml would have needed to be set to "ID" in order for the ID to be used to link up all the different entries, but perhaps the GUID fields are synced up between the callque and calltrack tables and you can use those to if you want to link up the entries in different tables?

 

Easiest may be to just update system with vgDialListLoad attached to this post. This version fixes the insert so that both ID and GUID are saved in the calltrack table when the zConfigXml_sDialer_OutDialQue_porttouse_LinkField entry is set to Disable in the Config.xml

 

To update just unzip and place .exe in VoiceGuide directory. (backup/rename previous vgDialListLoad.exe first)



#3 ID2016 15 March 2017 - 02:19 AM

This advice broke loader completely. Even when I reversed to the original loader, its not working anymore. What do i need to do now?



#4 SupportTeam 15 March 2017 - 07:14 AM

Could you please advise waht isn't working on this system?

 

Does the Call Loader application start?

 

Are the calls being loaded into the database?

 

Please try running both versions of Telephone Number Loader (one at a time) and then .ZIP up and post the DialListLoad traces from VoiceGuide's directory. We can then see what is happening on the system.



#5 ID2016 16 March 2017 - 01:49 PM

I need help asap. Weare going live in a few days but I cannot make any calls anymore after I installed recommende loaded . Old loader produce the same error. Please see an attachment - both loader generate the same error.

I am attaching error logs, vg.ini, config, mysql stored procedure with insert statement. 

I was given trial license for 4 VOIP lines that expires soon.

 

Please provide clear plan how i can fix VG. My insert statement inserts data into outdialque table but nothing is working.

 

This is my sql stored pr:

 

CREATE DEFINER=`root`@`localhost` PROCEDURE `readPin`(IN ivrPhone VARCHAR(11) , IN ivrPin VARCHAR(20), IN ivrSite VARCHAR(20))
BEGIN
 
insert into callque (phonenumber, phonenumberprefix, activatetime, 
       TimeStart_Mon,TimeStop_Mon,TimeStart_Tue,TimeStop_Tue,TimeStart_Wed,TimeStop_Wed,
       TimeStart_Thu ,TimeStop_Thu ,TimeStart_Fri,TimeStop_Fri,
       TimeStart_Sat,TimeStop_Sat,TimeStart_Sun,TimeStop_Sun, 
       campaignname, priority, onanswerlive,
       onanswermachine, onnotanswered, onretriesexhausted, answertimeout, retriesleft, 
       retriesdelay, rv, calloptions, escalationcalls)
       values(ivrPhone, '9', curdate(), 
       1,2359,1,2359,1,2359,1,2359,1,2359,1,2359,1,2359,
       'MyHealthPin', 1, 
       'C:\\Program Files (x86)\\VoiceGuide\\Scripts\\ReadPin\\IvrPin.vgs',
       'C:\\Program Files (x86)\\VoiceGuide\\Scripts\\ReadPin\\IvrPin.vgs',
       '', '', 60, 1, 10, 
       '[ivrPhone]{'+ivrPhone+'}[IvrPin]{'+ivrPin+'}[IvrSite]{'+ivrSite+'}', '', '');
 
 
END


#6 SupportTeam 16 March 2017 - 09:03 PM

Traces show outgoing calls are attempted, but the numbers loaded do not have the @IPADDRESS appended to them.

 

We can see in traces this:

 

    Line 590: 225217.711   9   3   1 state Dialing (auto) 92489789145
    Line 747: 225317.053   9   3   1 state Dialing (auto) 912489789145

 

    Line 641: 232434.395   9   3   1 state Dialing (auto) 912489789145
    Line 803: 232440.483   9   3   1 state Dialing (auto) 912489789145
    Line 935: 232441.504   9   3   1 state Dialing (auto) 912489789145
    Line 1067: 232442.522   9   3   1 state Dialing (auto) 912489789145
    Line 1198: 232443.535   9   3   1 state Dialing (auto) 912489789145

 

please ensure number specified is a fully qualified VoIP number with the IP address appended.

 

 

Regarding the loader application, please stop VoiceGuide service and exit all programs and then and delete the vgDialListLoad.exe from VoiceGuide directory.

 

Once deleted the please the install of the latest version of VoiceGuide over the top of current install. This will ensure the vgDialListLoad.exe  as included in VoiceGuide distribution ins placed on your system.

Still it looks like your insert SQL will be fine once the number is fixed up, so you may not need to use the vgDialListLoad.exe to load the calls anyway.



#7 ID2016 17 March 2017 - 01:23 AM

I do not not understand you response about @IPADDRESS.

The config file has all this info. I have 4 ipaddresses for VOIP. What is missing?

Did you look into my config.xml? 



#8 SupportTeam 17 March 2017 - 04:05 AM

Please see:

 

http://voiceguide.co...2031#entry42031

 

When loading a VoIP call into system you need to specify through which VoIP gateway/switch/etc that call is to be sent out through.

 

And the VoIP Switch / PBX / Gateway then forwards that VoIP call on to next VoIP Switch / PBX / Gateway according to its own rules.

 

VoIP number is specified as:

 

number@ipaddress

 

eg:

 

912489789145@10.231.234.19

 

10.231.234.19 is the IP address of your VoIP Switch / PBX / Gateway that we can see you have used before.

 

In the traces attached in the first post of this thread (0306_ktTts.zip) we can see that many outgoing calls were made from this system by routing them out through the 10.231.234.19 IP address



#9 ID2016 17 March 2017 - 07:30 AM

Attached File  0316_1345_vgEngine.zip   631.37KB   34 downloadsBu I have 4 IP addresses -> 4 channels. I can not choose in advance one of them when I insert a record per the phone call in outdialque table.

 

I am using Mysql stored procedure to insert the phone number with RV into outdialque table.

It should be able to call using any of 4 IPs designated to voip. How can I assign one? Please see my stored procedure. It has only phone and IP address. You said earlier it should work as it is.  Please send me config.xml that I should have if the one I attached is incorrect. 

 

insert into callque (phonenumber, phonenumberprefix, activatetime, 
       TimeStart_Mon,TimeStop_Mon,TimeStart_Tue,TimeStop_Tue,TimeStart_Wed,TimeStop_Wed,
       TimeStart_Thu ,TimeStop_Thu ,TimeStart_Fri,TimeStop_Fri,
       TimeStart_Sat,TimeStop_Sat,TimeStart_Sun,TimeStop_Sun, 
       campaignname, priority, onanswerlive,
       onanswermachine, onnotanswered, onretriesexhausted, answertimeout, retriesleft, 
       retriesdelay, rv, calloptions, escalationcalls)
       values(ivrPhone, '9', curdate(), 
       1,2359,1,2359,1,2359,1,2359,1,2359,1,2359,1,2359,
       'MyHealthPin', 1, 
       'C:\\Program Files (x86)\\VoiceGuide\\Scripts\\ReadPin\\IvrPin.vgs',
       'C:\\Program Files (x86)\\VoiceGuide\\Scripts\\ReadPin\\IvrPin.vgs',
       '', '', 60, 1, 10, 
       '[ivrPhone]{'+ivrPhone+'}[IvrPin]{'+ivrPin+'}[IvrSite]{'+ivrSite+'}', '', '');
 

I also downloaded the newer version of VG 7.5.8 - it was changed after I had the issue with Loaded.

 

Attaching logs files.

 

 



#10 SupportTeam 17 March 2017 - 08:23 AM

There is no need to have an IP address 'per channel' (ie. a separate IP address for each simultaneous call). Many calls can be sent through one "IP Address".

 

Can you please describe your setup in more detail. What device(s) are thse 4 IP adresses assigned to ?



#11 SupportTeam 17 March 2017 - 08:28 AM

Also, traces now shows that there are currently issues with your Config.xml file:

134835.022   0       vgDb_ProviderInvariant Db_LoadConfig call
134835.027     ERROR 7.5.6267.23386 Db_LoadConfig xmlConfigFile.Load : The 'Channel' start tag on line 34 position 2 does not match the end tag of 'Channels'. Line 42, position 3.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
   at System.Xml.XmlTextReaderImpl.ThrowTagMismatch(NodeData startTag)
   at System.Xml.XmlTextReaderImpl.ParseEndElement()
   at System.Xml.XmlTextReaderImpl.ParseElementContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
   at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
   at System.Xml.XmlDocument.Load(XmlReader reader)
   at System.Xml.XmlDocument.Load(String filename)
   at ..()
134835.027   0       config.xml read: /VoiceGuideConfig/Dialer
134835.027           db    config SelectNodes(/VoiceGuideConfig/Dialer) returned no nodes

so looks like right now the Config.xml cannot be read in, so this system is not even connecting to your MySQL backend database.

 

Pleas check your Config.xml for correct syntax.



#12 ID2016 17 March 2017 - 09:12 AM

Attached File  3162017.zip   744bytes   36 downloadsAttached File  0316_1803_vgDialListLoad.zip   118.64KB   38 downloadsI strongly believe there is a problem with newest version VG 7.5.8. No matter what I put into config.xml, the logs have the same error.

 

As result of these actions - replacement telephone loader, installation of VG 7.5.8, I cannot get anything into outdialque table from Loader. Neither I can dial when run stored procedure .

 

Need resolution ASAP.



#13 SupportTeam 17 March 2017 - 10:46 AM

The Config.xml now looks fine and the latest traces from the set of provided trace no longer show any Config.xml errors - the early traces in the set: 0316_1346_vgEngine.txt and 0316_1802_vgEngine.txt show the Config.xml error, but the more recent 0316_1826_vgEngine.txt and 0316_1841_vgEngine.txt don't show the config.xml error, and show that connection to MySQL database was done OK:

184106.598  15               Db_Open GetFactory call [MySql.Data.MySqlClient]
184106.601  15               Db_Open sDbName=[outdialque]
184106.601  15               Db_Open CreateConnection call
184106.611  15               Db_Open CreateConnection returned. conn=MySql.Data.MySqlClient.MySqlConnection, this=ktlib.vgDb.vgDb_ProviderInvariant
184106.611  15               Db_Open sConnString in.len=86, rvreplaced.len=87
184106.620  15               Db_Open conn.Open call
184106.727  15               Db_Open conn.Open returned
184106.728  15               Db_TestTables start, conn.DataSource=localhost, Provider=MySql.Data.MySqlClient
184106.728  15               Db_TestTables callque ExecuteScalar SELECT COUNT(*) FROM callque call (default)
184106.732  15               Db_TestTables callque ExecuteScalar SELECT COUNT(*) FROM callque returned iCount=0
184106.732  15               Db_TestTables calltrack ExecuteScalar SELECT COUNT(*) FROM calltrack call (default)
184106.735  15               Db_TestTables calltrack ExecuteScalar SELECT COUNT(*) FROM calltrack returned iCount=66
184106.735  15               Db_TestTables returned ok
184106.735  15               Db_Open DbCommandsParamteresInit next. conn=MySql.Data.MySqlClient.MySqlConnection

Two vgDialListLoad traces were included in provided traces:

 

The 0316_1803_vgDialListLoad.txt trace shows that the Dial List Loder app when started at 6:03PM could not read the Config.xml, so would not have connected to the MySQL database, so all the calls loaded between 18:03 and 18:43 using that instance of app were placed into default databsae (SQLite file C:\Program Files (x86)\VoiceGuide\data\vgDb.db) :

180307.865   0       vgDb_ProviderInvariant Db_LoadConfig call
180307.872     ERROR 7.5.6267.23386 Db_LoadConfig xmlConfigFile.Load : The 'Channel' start tag on line 34 position 2 does not match the end tag of 'Channels'. Line 42, position 3.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)
   at System.Xml.XmlTextReaderImpl.ThrowTagMismatch(NodeData startTag)
   at System.Xml.XmlTextReaderImpl.ParseEndElement()
   at System.Xml.XmlTextReaderImpl.ParseElementContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
   at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
   at System.Xml.XmlDocument.Load(XmlReader reader)
   at System.Xml.XmlDocument.Load(String filename)
   at ..()
180307.872   0       config.xml read: /VoiceGuideConfig/Dialer

The 0316_1902_vgDialListLoad.txt trace file is missing the startup section, so we cannot see to what database it connected. If there were problems with Config.xml at that time then again this Dial List Load instance would not have connected to the MySQL database.

 

Suggest using MySQL Worbench or other similar tools to confirm if calls are being laded into database thatyou expect them to be loaded. The 'calltrack' table is probably the best palce to monitor new additons made from the Dial List Load app.



#14 SupportTeam 17 March 2017 - 11:01 AM

In addition, the 0316_1826_vgEngine.txt and 0316_1841_vgEngine.txt traces show outgoing call attempts, but the were made to numbers that did not even have an IP address in them. So they all failed as could not be VoIP routed:

    Line 647: 182632.493   9   3   1 state Dialing (auto) 9123462462
    Line 770: 182633.507   9   3   1 state Dialing (auto) 9123462462
    Line 901: 182634.515   9   3   1 state Dialing (auto) 9123462462
    Line 1034: 183632.446   9   3   1 state Dialing (auto) 9123462462
    Line 1172: 183633.461   9   3   1 state Dialing (auto) 9123462462
    Line 1308: 183635.494   9   3   1 state Dialing (auto) 9123462462

    Line 632: 184921.188   9   3   1 state Dialing (auto) 9236463575735
    Line 768: 185921.140   9   3   1 state Dialing (auto) 9236463575735

guess the 9123462462 calls were old calls still in database that were getting redialed, and the 9236463575735 call was a new call loaded direct into database (?)

 

The DialListLoad traces show that loaded calls did include IP address, but as per previous post, it looks like these calls were not loaded into the MySQL database:

0316_1803_vgDialListLoad.txt
    Line 206: 180316.835   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,a3fe0b6c-325f-4e50-a2e0-17cfbffcf5e1,]
    Line 212: 180316.843   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,b1e695b0-b8fd-4664-ba05-f9965a8f7088,]
    Line 218: 180316.844   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,ef2d7e8d-cf1a-4eeb-9650-b2fe0fbbb5a2,]
    Line 224: 180316.845   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,f0d43931-12b7-4694-8649-d02d6c7fb297,]
    Line 371: 180826.658   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,8ab44e5c-086f-4e29-8df0-7b44165d4fc2,]
    Line 377: 180826.660   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,05cbac14-43d6-4061-b508-8ff60c4072c5,]
    Line 383: 180826.661   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,3bf610e2-70c0-433a-ad5b-fe35f554dd4a,]
    Line 389: 180826.662   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,c9d6bbc5-14ee-4228-8f82-d77883e4ad68,]
    Line 537: 181207.621   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,d6c0f319-bb42-440e-b2c4-9c4eb3d28c22,]
    Line 543: 181207.624   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,6a326ba3-dd87-468d-ab6d-75996cc702b2,]
    Line 549: 181207.624   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,92f223d1-33c5-4425-bb6c-55b6b86ff524,]
    Line 555: 181207.625   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,7b4efec7-72c3-487b-aa2e-75d063325725,]
    Line 732: 182638.770   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,c07f4e6a-b734-4059-8b36-4446fd95b9de,]
    Line 738: 182638.772   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,9e61361d-96cb-4287-a6eb-59d203b8d77a,]
    Line 744: 182638.773   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,8206400a-4f67-4ddb-8ddc-e2054fe54629,]
    Line 750: 182638.774   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,2f02b492-4d03-4200-9843-5051804936c5,]
    Line 912: 183959.246   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,92cdd559-2bd9-4f4d-9dbe-77a9a18bd40d,]
    Line 918: 183959.248   0       dial  cmd_callque_Insert ExecuteNonQuery [912489789145@10.231.234.19,,f559208e-cd53-4967-8f96-14a7957b2553,]
etc.


0316_1902_vgDialListLoad.txt 
    Line 106: 190305.395   0       dial  cmd_callque_Insert ExecuteNonQuery [92489789145@10.231.234.19,,6e0db6f0-d567-429b-867c-c3cd9e18a1fa,]
    Line 273: 190341.425   0       dial  cmd_callque_Insert ExecuteNonQuery [92489789145@10.231.234.19,,be2186d8-221c-4aec-ada6-473c42e0efc0,]


#15 ID2016 18 March 2017 - 06:07 AM

i was able to fix the issues