PhilRobert Report post Posted 04/01/2004 06:00 PM Hi. I would like to know if it is possible to run a script without getting an incoming call that starts it... What I would like to do is the following : I have a database which is filled by another program with a list of numbers to call. I would like my script to start every 10 minutes and query the database, then, if there are records in, launch the calls and delete the records. Every help/comments/ideas are welcome. Thanks. Share this post Link to post
SupportTeam Report post Posted 04/01/2004 11:10 PM This is basically what VG Dialer does. The database VG Dialer uses is OutDialQue.mdb, located in VG's \data\ subdirectory. When any entries are placed in this database VG Dialer will then make the calls. Sounds like all that you need to do is to have your program either write directly into OutDialQue.mdb, or have a small app which just copies data from your database into OutDialQue.mdb Share this post Link to post
PhilRobert Report post Posted 04/02/2004 01:59 PM Can I send messages to a pager using the dialer? Share this post Link to post
PhilRobert Report post Posted 04/02/2004 03:28 PM And what exactly will make the dialer start the calls? Is it always waiting for an input in the database and as soon as it picks up one, it starts dailing or do I have another program to start or something like that? Share this post Link to post
SupportTeam Report post Posted 04/02/2004 10:22 PM Is it always waiting for an input in the database and as soon as it picks up one, it starts dailing Yes. For an example of scheduling calls to pager - and a bug fix which you will need with v5.2.1 please read: http://www.voiceguide.com/forums/index.php...?showtopic=1360 Share this post Link to post
PhilRobert Report post Posted 04/05/2004 05:29 PM I installed the version 5.2.1020, but it seems VG has problems sending a message to a pager. Looks like it dials but is unable to dial the numerical message and it hangs up, deleting the record in the database but I never get the pager message... I tested it on a cell phone, so I know the program really calls, that's why I think it's probably when dialing the numerical message that the problem occurs. Here's the log of the call : 114709,16 7 dial [49,18009655874,404051147,1,2359,MoTuWeThFrSaSu,,dxxxB1C3,,1,1234567,DIAL_PAGER_ UMERIC,DIAL_PAGER_NUMERIC,none,120,4,2,,none] 114709,16 0 dial callque update id=49 next call time 0404051149 114709,16 0 dial callque DB update returned 114709,16 7 dial found entry: tel[18009655874] ann[1234567] vgs[DIAL_PAGER_NUMERIC] am[DIAL_PAGER_NUMERIC] 114709,16 7 Dialing: 18009655874 114709,16 7 MakeCall => 65901 114709,16 7 TimeoutSet 120 EV_TIMEOUT_MAKECALL_NORESPONSE 114709,16 7 TapiCbTrigSet 65901 7002 114709,91 7 tapi Reply (LineEvReply) ok 65901 0 114709,91 7 TapiCbTrigClear 114709,91 7 linedevstate 2048 0 0 114709,91 7 callstate DIALTONE 66227 0 0 114709,91 7 callstate DIALING 66227 0 0 114709,91 7 callstate PROCEEDING 66227 0 0 114709,92 7 callinfo CALLEDID 114709,92 7 callinfo REASON 114709,92 7 Lev_CallerID [0000,] 114709,92 7 callinfo ORIGIN 114719,30 7 callstate DISCONNECTED 66227,16,0 114719,30 7 ScriptEventCode 9250 iLineState=5200 114719,30 7 LsWaitAfterDialingOut EV_REMOTEPARTY_DISCONNECT 114719,30 7 Sending Numeric Pager Message 114719,30 7 TimeoutSet 2 EV_TIMEOUT_WAITBEFORESENDINGPAGERMESSAGE 114719,30 0 dial callque delete id=49 114719,30 7 AddRVns [OutDial_Result]{Contacted_Pager} 114721,48 7 Timer fired EV_TIMEOUT_WAITBEFORESENDINGPAGERMESSAGE 114721,48 7 ScriptEventCode 9010 iLineState=1140 114721,48 7 LsOutboundCall_NumericPager EV_TIMEOUT_WAITBEFORESENDINGPAGERMESSAGE 114721,48 7 Playing numeric pager message:1234567 114721,48 7 TimeoutSet 30 EV_TIMEOUT_HANGUP 114721,48 7 tapic lineGenerateDigits(66227,1234567,0) => LINEERR_INVALCALLSTATE [8000001C] 114721,48 7 rv add [Hangup Time]{2004-04-05 11:47:21} 114721,48 7 Hanging up call... [lineGenerateDigits ret=-2147483620] 114721,48 7 RecSoundStop ok 114721,48 7 PlaySoundStop err=0 114721,48 7 TimeoutSet 2 EV_TIMEOUT_WAITFORIDLEAFTERLINEDROP 114721,48 7 Waiting for a call... 114721,50 7 fnHangupCall end 114721,53 7 linedevstate 2048 0 0 114721,53 7 callstate IDLE 66227 0 0 114721,53 7 WorkingMode@Idle= 114721,53 7 TimeoutClear 114721,53 7 LineState(iLineId).iVgsIdx = 0 114721,53 7 TimeoutSet 1 EV_TIMEOUT_TIMETOREINITLINE 114721,53 7 tapi Reply (LineEvReply) ok 65833 0 114722,59 7 Timer fired EV_TIMEOUT_TIMETOREINITLINE 114722,59 7 ScriptEventCode 9008 iLineState=900 114722,59 7 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE 114722,59 7 ReinitTelephony due to IDLE 114722,59 7 tapic lineDeallocateCall(MainCall:66227) 0 114722,75 7 lineOpen(7)=> 114722,75 7 Waiting for a call... 114722,75 7 LineHandle=66346 114722,75 7 TimeoutSet 3 EV_TIMEOUT_ATERIDLE_ALLOWOUT 114726,03 7 Timer fired EV_TIMEOUT_ATERIDLE_ALLOWOUT 114726,03 7 ScriptEventCode 9013 iLineState=900 121002,23 0 sys cleanup Start 121002,23 0 sys cleanup End 124002,23 0 sys cleanup Start 124002,23 0 sys cleanup End 131002,23 0 sys cleanup Start 131002,23 0 sys cleanup End Also, I'll attach the OutDialQue database so you can see if there's something wrong there... Oh yeah, by the way, I'm working with a D/4PCI Dialogic card under Windows 2000... Thanks for the help! = ) Share this post Link to post
SupportTeam Report post Posted 04/05/2004 11:31 PM Can you please try setting in VG.INI file, section [VGDialer] : AM_DetectionMode=Disabled then restart VG and try making call again. Share this post Link to post
PhilRobert Report post Posted 04/06/2004 01:48 PM Thanks, it works now! = ) Share this post Link to post
SupportTeam Report post Posted 04/07/2004 12:28 AM Updating your v5.2.1 with attached .exe should allow you to just specify "DISABLE" in the "Answering Machine" field - then Answering Machine detection will be disabled for just that call. This will allow you to go back to using AM_DetectionMode=Enabled in VG.INI file - so that any other outgoing voice calls can still do answering machine detection. VgMulti_5.2.1024.zip Share this post Link to post