Sql Server Based Dialer Not Runs

[Guest DiegoBellini]

Hi,

I have read the file of help later and have followed all the steps to perform an automatic dialer.

http://www.voiceguide.com/vghelp/source/ht...ialque_odbc.htm

 

The information that here one presents it's very poor.

You will be able to give me more information to configure this?

 

I have the table created in the database and already I have some data in the same one.

I do not because not works, nothing happens.

Then, they sending my ODBC, my VG.ini with the entry in the section VGDIALER, and the logs files, in order that they inform to me.

Thanks

Errors.zip

[SupportTeam]

Please update your system to VG v7.0.6 and post the traces from that version.

[Guest DiegoBellini]

Please update your system to VG v7.0.6 and post the traces from that version.

 

I has just updated my system to VG v7.0.6 and now nothing happens.

New.zip

[SupportTeam]

The vgEngine trace shows no attempt to read from any external OutDial queue. Have you setup the external OutDial queue source and configured the connect string to it in the VG.INI file?

 

 

The registration with sip.voipbuster.com was ok:

 

171735.734 5708 fn VoIPProvider_Register(protocol=SIP, reg_server=sip.voipbuster.com, reg_client=GLCIVRDEMO@sip.voipbuster.com, local_alias=GLCIVRDEMO@10.1.1.9, sH323SupportedPrefixes=)

171735.734 5708 TelDriver_VoIPProvider_Register IP_PROTOCOL_SIP reg=[server:sip.voipbuster.com, client:GLCIVRDEMO@sip.voipbuster.com, alias:GLCIVRDEMO@10.1.1.9] iptB1=1

171735.734 5708 gc_ReqService ok (iHmp_iptB1=1)

 

and you can see call from sip.voipbuster.com arriving on the system, but it is not answered because VG could not find the script to use.

 

 

The vgEngine trace shows that incoming calls are not answered as :

 

 

171735.703 5 13 OpenChanels could not load script [C:\Archivos de programa\VoiceGuide\Local\TeleCoopMain.vgs]

...

171829.390 9 3 NOTE: not answering as no script attached to line. (VgsIdx=-1}

 

[Guest DiegoBellini]

So, because the calls are not answered if the script exists. This it is the problem, but why it happens.

[SupportTeam]

You must specify a script in Config.xml that actually exists...

 

If you continue to have problems please post a trace showing the system startup and an incoming call in situation where you have specified a valid script in Config.xml