dennis_juel Report post Posted 10/30/2003 04:37 PM Hi 1. Problem I am using a Voicemodem to dial up with Voiceguide dialer. The problem is that if the person who receives the call answer fast “under 1 Seconds “ the dialer do not recognize that the phone is answered and then the voiceguide dialer hangs up the phone. If the person I slow “ over 1 S “ the dialer works fine and the script starts running. What can I do to solve this problem??? We are trying to find a dialogic card, but in the meantime before we acquire a dialogic card we must use a standard Voice modem. 2. Problem when the person receiving the call is slow “ over 2 seconds “ the script starts running and the wav file starts playing before the person has answered the phone. Best regards Dennis Udengaard Brewerygroup Denmark Dju@bryggerigruppen.dk Share this post Link to post
SupportTeam Report post Posted 10/30/2003 10:38 PM if the person who receives the call answer fast “under 1 Seconds “ the dialer do not recognize that the phone is answered and then the voiceguide dialer hangs up the phone Could you please post a copy of VoiceGuide's Debug Printout which captures the problem, this will allow us to see what is going wrong. (When running the script click on VoiceGuide's View menu and select 'Event Trace Log' option - any log information will then appear in this window. You must open the trace window before making the call.) when the person receiving the call is slow “ over 2 seconds “ the script starts running and the wav file starts playing before the person has answered the phone. Are you referring to the "Please press 1 to accept this call.." message? That message will play in a loop when a Voice modem is used - but if you have specified "none" for welcoming message then the script will start immediately. Share this post Link to post
dennis_juel Report post Posted 10/31/2003 10:25 AM this log is when tho phone is answered fast and voiceguide hangs op the phone.. 110302.61 0 dial callque update id=158 next call time 0310311108 110302.61 0 dial callque DB update returned 110302.61 0 dial found entry: tel[66851] ann[NONE] vgs[C:\Program Files\VoiceGuide\Ceres\BREWHOUSE\URTNEDSVALING\URTNEDSVALING.vgs] am[NONE] 110302.63 0 Calling MakeCallEx(66851) 110302.63 0 Dialing: 66851 110302.63 0 MakeCall => 66032 110302.63 0 TapiCbTrigSet 66032 7002 110302.63 0 tapi Reply (LineEvReply) ok 66032 0 110302.63 0 TapiCbTrigClear 110302.63 0 callstate DIALING 65980 0 0 110302.63 0 callstate PROCEEDING 65980 0 0 110313.52 0 LsWaitAfterDialingOut EV_TIMEOUT_MAKECALL_NORESPONSE 110313.52 0 dial callque update id=158 next call time 0310311108 110313.52 0 dial callque DB update returned 110313.52 0 Hanging up call... [EV_TIMEOUT_MAKECALL_NORESPONSE] 110313.52 0 RecSoundStop ok 110313.52 0 PlaySoundStop ok 110313.52 0 Waiting for a call... 110313.52 0 fnHangupCall end 110315.71 0 Hanging up call...(2) 110315.71 0 RecSoundStop ok 110315.71 0 PlaySoundStop ok 110315.71 0 Waiting for a call... 110315.71 0 fnHangupCall end 110315.71 0 LsAwaitingCalls EV_TIMEOUT_WAITFORIDLEAFTERLINEDROP 110315.71 0 tapi Reply (LineEvReply) ok 66014 0 110330.02 0 callstate DISCONNECTED 65980,1,0 110330.02 0 LsAwaitingCalls EV_REMOTEPARTY_DISCONNECT 110330.02 0 Hanging up call... 110330.02 0 RecSoundStop ok 110330.04 0 PlaySoundStop ok 110330.04 0 Waiting for a call... 110330.04 0 fnHangupCall end 110330.04 0 callstate IDLE 65980 0 0 110330.04 0 WorkingMode@Idle= 110330.04 0 LineState(iLineId).iVgsIdx = 0 110330.04 0 tapi Reply (LineEvReply) ok 66031 0 110330.05 0 tapi Reply (LineEvReply) ok 66049 0 110331.04 0 LsAwaitingCalls EV_TIMEOUT_TIMETOREINITLINE 110331.04 0 ReinitTelephony due to IDLE start 110331.04 0 tapic lineDeallocateCall(MainCall:65980) 0 110331.05 0 lineOpen(0) => 0 110331.05 0 Waiting for a call... 110331.05 0 lineOpen(0)LineHandle=66066 Share this post Link to post
SupportTeam Report post Posted 10/31/2003 01:45 PM Looks like the system is hanging up at the same time as it is trying to dial - how was this outbound call queued? The Answer timeout should be reasonable number (15 seconds at least) and it is now being set to 0. Share this post Link to post