Vg Stopped Making Calls After Using Dialer_Outdialqueadd

[Guest Jonah]

I used the following line of code to programatically add a record to the outdial que at approx 1:26PM. VoiceGuide stopped making outdial calls at this point until it was restarted. At that point it began outdialing all the records that were in the que. I see that there are some errors in the attached log. Is there something I am missing in the statement below? Thank you.

 

mobjVoiceguide.Dialer_OutDialQueAdd("3036141227", "", "", "0900", "2000", "MoTuWeThFrSaSu", "22,23,24,25,26", "", 1, C:\VoiceGuide\VGBones2010\VGScripts\VGStartCall_RMR.vgs, C:\VoiceGuide\VGBones2010\VGScripts\VGStartCall_RMR.vgs, "", C:\VoiceGuide\VGBones2010\VGStartCall\EXE\VGStartCall.exe $RV_LINEID RMR $RV[OutDial_Result] $RV[RepositoryID] $RV_CALLEDNUMBER, "", "25", 0, 120, [RepositoryID]={1821}, "", "")

0706_1129_vgEngine.zip

[SupportTeam]

The trace shows that the connection to the database which stores the outbound calls was lost, and hence the outbound calls could not be loaded.

 

Please update your system to current version of VoiceGuide. Current version will automatically try to reconnect to database if the connection has been lost for some reason.

[Guest Jonah]

I upgraded to the new version of VoiceGuide. VoiceGuide still crashed when records were imported but it did reconnect to the DB without a restart - which is a definate improvement. I'm still curious as to why it crashed. Attached are the logs. Let me know if you need more info.

0712_0943_vgEngine.zip

[SupportTeam]

Log shows that there is a number (about 10) of these errors towards end of log:

 

66410:100912.678 11 7 3 ERROR dial call found (autodialer) port= 3, ID/GUID=527101/4beed384-5b67-4a06-adc1-910528326113, tel=, diff=00:00:00 - not proceeding with call as tel number is empty

 

So looks like the telephone number to dial was not specified in the call entries loaded into the database.

 

The system otherwise looked like operating as normal. There is no evidence of any 'crash'. Please don't say 'crash' if you just mean 'not making calls'. The term 'crash' means something else.

[Guest Jonah]

Same issue happened again. All I did was to add records to the outdial que through mobjVoiceguide.Dialer_OutDialQueAdd and VoiceGuide stopped making calls. This happened ata approximately 2:10pm. VoiceGuide did recover from this error but I am still concerned as to why it stopped making calls / lost connectivity to the DB. Logs are attached. Please let me know if you need any more info.

[Guest Jonah]

forgot to add the logfiles

[SupportTeam]

Log files did not get attached to the previous post. Can you please try attaching them again.

[Guest Jonah]

here they are

0727_1410_vgEngine.zip

[SupportTeam]

Trace shows that errors were sometime encountered when the Dialer_OutDialQueAdd function was called from external program and many of the loads were not made.

These loads were made at around 14:13:00 - 14:13:02

 

System did continue to make calls which were already in the outdial database:

 

141306.371 6 31 11 state Dialing (auto) 3039852944

141310.292 6 13 5 state Dialing (auto) 13037330182

141310.480 6 46 16 state Dialing (auto) 12095237678

141310.480 6 52 18 state Dialing (auto) 12095237757

 

We will next look into why the Dialer_OutDialQueAdd function was unable to actually load the supplied calls into the outdial database.

[Guest Jonah]

Same thing happened again this morning. However this time it required VG to be restarted before it began making calls.

 

Logs are attached.

 

Thank you

0802_1032_vgEngine.zip

[SupportTeam]

Traces show that the connection to the OutDial database was broken and for some reason could not be re-established.

 

Rest of system worked fine and accepted and processed incoming calls as normal, just no outbound calls were made.

 

What external database are you using? SQL Server? Which version?

 

When making the outbound calls do you want to restrict the outbound calls to be made on specific channels of the T1 ISDN trunks, or can all the loaded calls be made on any channel?

 

 

from 0712_0943_vgEngine:

 

094349.703 5 System.Data.SqlClient : SqlClient Data Provider, .Net Framework Data Provider for SqlServer, System.Data.SqlClient.SqlClientFactory, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

...

094349.781 5 config.xml read: /VoiceGuideConfig/Dialer

094349.781 5 ReadXmlNodesSubEntryintoString(OutDialQue_porttouse_LinkField) node not found in: System.Xml.XmlElement

094349.781 5 ReadXmlNodesSubEntryintoString(OutDialQue_PortToUse_LinkField) node not found in: System.Xml.XmlElement

094349.781 5 ReadXmlNodesSubEntryintoString(OutDialQue_SQL_EscapeChar_Quote) node not found in: System.Xml.XmlElement

094349.781 5 ReadXmlNodesSubEntryintoString(OutDialQue_SQL_EscapeChar_DblQuote) node not found in: System.Xml.XmlElement

094349.781 5 db config OutDialQue_ADODB_Provider = System.Data.SqlClient

094349.781 5 db config OutDialQue_Database = OutDialQue2010

094349.781 5 db config OutDialQue_ConnectString.len = 85

094349.781 5 db config OutDialQue_SqlPrefix =

094349.781 5 db config OutDialQue_SqlSuffix =

094349.781 5 db config OutDialQue_porttouse_LinkField = (deprecated. Use OutDialQue_PortToUse_LinkField)

094349.781 5 db config OutDialQue_PortToUse_LinkField =

094349.781 5 db config zConfigXml_sDialer_OutDialQue_porttouse_LinkField = GUID (default for provider = System.Data.SqlClient)

094349.781 5 vgDb_ProviderInvariant Db_Open call

094349.921 5 Db_Open GetFactory call [system.Data.SqlClient]

094350.093 5 Db_Open sDbName=[OutDialQue2010]

094350.093 5 Db_Open CreateConnection call

094350.906 5 Db_Open CreateConnection returned. conn=System.Data.SqlClient.SqlConnection, this=ktlib.vgDb.vgDb_ProviderInvariant

094350.906 5 Db_Open sConnString in.len=85, rvreplaced.len=90

094350.984 5 Db_Open conn.Open call

094352.140 5 Db_Open conn.Open returned

094352.156 5 Db_TestTables start

094352.156 5 Db_TestTables ExecuteScalar call

094352.234 5 Db_TestTables objExecScalar=469

094352.234 5 Db_TestTables ExecuteScalar returned

094352.234 5 Db_TestTables returned ok

094352.234 5 Db_Open DbCommandsParamteresInit next. conn=System.Data.SqlClient.SqlConnection

094352.250 5 dial cmd_UpdateDateAndRetries init ok

[Guest Jonah]

I am using SQL Server 2008 and I do need to restrict the ports because I have several projects running, each of which needs to be running on a select number of ports.