Jump to content


< Back to Forum


 

Vg Arrete De Foncrionner.


  • Please log in to reply

#1 JFSauriol 22 September 2015 - 01:48 AM

Attached File  VgEngine.zip   32.02MB   58 downloadsAttached File  0920_ktTel.zip   21.31MB   56 downloadsBonjour. Regulierement VG cesse de fonctionner sans aucune raison apparente. Cela commence par une ligne, ensuite une autre, etc. La seule option que j'ai trouvé c'est de rebooter l'ordinateur. Pour quelques temps une heure ou moins VG fonctionne normalement. Est-ce que c'est mon fournisseur de telephones IP ou le fournisseur internet ou VG ou HMP3?

 

J'utilise HMO3 ver. 347 et VG ver. 7.4.4. Ce systeme ne sert qu'a faire des appels de sondage et aucune autre chose.

 

Jean Francois Sauriol

 

 



#2 SupportTeam 22 September 2015 - 09:53 PM

Google Translate:

 

Regularly VG stops working for no apparent reason . This starts with a line , then another , etc. The only option I've found is to reboot the computer. For some time an hour or less VG operating normally. Is it my IP Phones provider or internet provider or VG or HMP3 ?

 
I use HMO3 ver. 347 and VG ver. 7.4.4 . This system only serves to make the survey calls and nothing else .



#3 SupportTeam 22 September 2015 - 10:06 PM

We can see that between 11AM and 6:30PM this system made in excess of 23,000 outgoing calls.

 

Can give us some specific examples of what times and lines/ports to look at?

 

Also, Please update this system to newer version of VoiceGuide: [removed] and post traces captured when that newer version is used.

 

 

To change from one release of VoiceGuide v7 to another:

1. Stop VoiceGuide Service and exit all VoiceGuide programs. (eg Script Designer, Voicemail Manager, etc) and all other programs.

2. Run the VoiceGuide install and install into same directory as existing installation. (Do NOT uninstall the previous VoiceGuide installation).

3. Start  VoiceGuide service.

 

Running a VoiceGuide install over the top of an existing install will NOT overwrite existing configuration or license files (Config.xml, ConfigLine.xml, VG.INI, VmBoxList.xml, etc) and will not remove any of users script or sound files, and will not remove any log files etc.



#4 JFSauriol 23 September 2015 - 09:50 AM

Voici. J'ai fait l'installation tel que recommandé. De plus j'ai installé la mise a jour HMP 357 de Dialogic.

 

Je vous envoie aussi le fichier Config que j'ai renommé Config_VG pour ne pas disperser des informations sensibles.

 

Quels sont vos conseils?

 

  • Attached File  VG.zip   342.63KB   55 downloads


#5 SupportTeam 23 September 2015 - 01:13 PM

Google Translate:

 

Here you are. I made the installation as recommended. Also I installed the update Dialogic HMP 357 .

I also send you the Config file I renamed Config_VG not disperse sensitive information.

What are your tips ?



#6 SupportTeam 23 September 2015 - 07:28 PM

Could you please post the vgEngine and ktTel traces that capture VoiceGuide service startup. We an then see what happened at VoiceGuide service startup time.

 

(Please .ZIP up all traces before posting)



#7 JFSauriol 23 September 2015 - 11:39 PM

Voila. J'ai rebooté l'ordinateur avant de vous envoyer ces fichiers.

  • Attached File  log.zip   14.89KB   59 downloads


#8 SupportTeam 24 September 2015 - 07:25 AM

Google Translate:

 

Here is. I rebooted the computer before you send these files.



#9 SupportTeam 24 September 2015 - 08:00 AM

ktTel trace shows that the Dialogic drivers are returning an error when starting:

139 093034.332  2516     ERROR gc_start
140 093034.333  2516   2       StartDialogicGlobalCall returned -1

The Dialogic RTF logs may give more information as to why the Dialogic drivers are not starting up, but probably the quickest way to resolve this is to fully uninstall the Dialogic HMP, and then install it again. 

Please make sure to reboot the computer after uninstalling - as per Dialogic HMP instructions shown on screen at end of install - and then run the new Dialogic HMP install after the reboot.

 

Probably best to install the SU347 HMP version, which you know was starting OK and making calls on this system before. 

 

Also, could you please advise which version of Windows is used on this system? Windows 7 32-bit ?


#10 SupportTeam 24 September 2015 - 10:33 AM

Also, looking at previously supplied traces it looks like you have not configured any script to run when an incoming call arrives.

 

There are however calls arriving at this system.

 

You must define a script to handle those incoming calls - even if the script just consists of a single 'Hangup' type module which would hangup the incoming call right away.

 

 

From ktTel, showing incoming calls:

Line 1895: 894 104521.860  5528   3       ani: 951@184.160.155.7 orig: 951@184.160.155.7 name:  dnis: 900972599311308@184.160.155.7 dest: 900972599311308@184.160.155.7
Line 98533: 532 112455.292  5528  40       ani: 101@184.160.155.7 orig: 101@184.160.155.7 name:  dnis: 00972599771536@184.160.155.7 dest: 00972599771536@184.160.155.7
Line 162232: 231 114434.710  5528  28       ani: 55522@184.160.155.7 orig: 55522@184.160.155.7 name:  dnis: 910972599161896@184.160.155.7 dest: 910972599161896@184.160.155.7
Line 162324: 323 114438.381  5528  25       ani: 55522@184.160.155.7 orig: 55522@184.160.155.7 name:  dnis: 011972599161896@184.160.155.7 dest: 011972599161896@184.160.155.7
Line 162397: 396 114439.593  5528  10       ani: 55522@184.160.155.7 orig: 55522@184.160.155.7 name:  dnis: 0011972599161896@184.160.155.7 dest: 0011972599161896@184.160.155.7
Line 162512: 511 114441.519  5528  34       ani: 55522@184.160.155.7 orig: 55522@184.160.155.7 name:  dnis: 0001972599161896@184.160.155.7 dest: 0001972599161896@184.160.155.7
Line 162646: 645 114442.770  5528  31       ani: 55522@184.160.155.7 orig: 55522@184.160.155.7 name:  dnis: 002972599161896@184.160.155.7 dest: 002972599161896@184.160.155.7
Line 162730: 729 114444.056  5528   7       ani: 55522@184.160.155.7 orig: 55522@184.160.155.7 name:  dnis: 01100972599161896@184.160.155.7 dest: 01100972599161896@184.160.155.7
Line 331134: 683 124951.302  5280  37       ani: 1001@184.160.155.7 orig: 1001@184.160.155.7 name:  dnis: *011972592168757@184.160.155.7 dest: *011972592168757@184.160.155.7
Line 533124: 673 134126.391  5280  28       ani: 1001@184.160.155.7 orig: 1001@184.160.155.7 name:  dnis: +011972592168693@184.160.155.7 dest: +011972592168693@184.160.155.7
Line 1275589: 138 152644.714  5280  40       ani: 3114@184.160.155.7 orig: 3114@184.160.155.7 name:  dnis: +11972592480350@184.160.155.7 dest: +11972592480350@184.160.155.7
Line 1275630: 179 161746.259  5280  13       ani: 3114@184.160.155.7 orig: 3114@184.160.155.7 name:  dnis: 8011972592480350@184.160.155.7 dest: 8011972592480350@184.160.155.7
Line 1284906: 274 151239.836  5084   3       ani: 1001@184.160.155.7 orig: 1001@184.160.155.7 name:  dnis: +011972592168757@184.160.155.7 dest: +011972592168757@184.160.155.7
Line 1489600: 968 163208.977  5084  31       ani: 4194@184.160.155.7 orig: 4194@184.160.155.7 name:  dnis: +9011972592480350@184.160.155.7 dest: +9011972592480350@184.160.155.7
Line 2077073: 555 190600.734  4832  13       ani: 1001@184.160.155.7 orig: 1001@184.160.155.7 name:  dnis: *972592168757@184.160.155.7 dest: *972592168757@184.160.155.7
Line 2077114: 596 195842.671  4832  10       ani: 1001@184.160.155.7 orig: 1001@184.160.155.7 name:  dnis: .972592168693@184.160.155.7 dest: .972592168693@184.160.155.7
Line 2077155: 637 225919.845  4832  16       ani: 1001@184.160.155.7 orig: 1001@184.160.155.7 name:  dnis: .972592168757@184.160.155.7 dest: .972592168757@184.160.155.7
Line 2077196: 678 235144.253  4832  28       ani: 1001@184.160.155.7 orig: 1001@184.160.155.7 name:  dnis: +9011972592168693@184.160.155.7 dest: +9011972592168693@184.160.155.7


#11 JFSauriol 26 September 2015 - 05:59 AM

 

ktTel trace shows that the Dialogic drivers are returning an error when starting:

139 093034.332  2516     ERROR gc_start
140 093034.333  2516   2       StartDialogicGlobalCall returned -1

The Dialogic RTF logs may give more information as to why the Dialogic drivers are not starting up, but probably the quickest way to resolve this is to fully uninstall the Dialogic HMP, and then install it again. 

Please make sure to reboot the computer after uninstalling - as per Dialogic HMP instructions shown on screen at end of install - and then run the new Dialogic HMP install after the reboot.

 

Probably best to install the SU347 HMP version, which you know was starting OK and making calls on this system before. 

 

Also, could you please advise which version of Windows is used on this system? Windows 7 32-bit ?

 

Yes I use win 7 32 bits. 

 

For incomming call, I do I handle this? I can make the module in the script designer, and after what I should do? Did I have to put something in my config file? 

By the way VG is working now whit HMP 3 V 347



#12 SupportTeam 26 September 2015 - 08:02 AM

Each Config.xml <Channel> section needs a <Script> entry. eg:

 

<Script>C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs</Script>

 

It looks like these <Script> entries were removed from the Config.xml on your system at some stage. They should be put back so that the system knows what to do when an incoming call arrives.



#13 JFSauriol 26 September 2015 - 09:19 AM

Thanks so much.