Calls But Hangs Up On First Ring

[Guest u4910]

I have been using VG5 with modem but have now switched to VG7 with Dialogic and trying to reuse my existing scripts.

I am making outbound calls and playing a wav file.

When it calls a number, it dials, and hangs up on first ring. I'm not sure why.

Here is my xml file:

 

<OutDialEntry> <PhoneNumber>612-1234</PhoneNumber> <PhoneNumberPrefix></PhoneNumberPrefix> <ActivateTime></ActivateTime> <DayTimeStart>0800</DayTimeStart> <DayTimeStop>2359</DayTimeStop> <DaysCallAllowed>MoTuWeThFrSaSu</DaysCallAllowed> <LineSelection></LineSelection> <CampaignName></CampaignName> <Priority></Priority> <OnAnswerLive>e:\ivr\outbound1\1111_1.wav</OnAnswerLive> <OnAnswerMachine>e:\ivr\outbound1\1111_1.wav</OnAnswerMachine> <OnNotAnswered></OnNotAnswered> <OnRetriesExhausted></OnRetriesExhausted> <AnswerTimeout>20</AnswerTimeout> <RetriesLeft></RetriesLeft> <RetriesDelay></RetriesDelay> <RV></RV> <CallOptions></CallOptions> <Escalation></Escalation> </OutDialEntry>

1227_1202_vgEngine.txt

1227_ktTel.txt

[SupportTeam]

Trace shows that 3 seconds after dialing the number 3196880 the Dialogic card reported that it heard a "SIT Tone" (otherwise known as an 'Operator tone' or 'Operator intercept tone' or 'Tri-tone'). Phone company plays a SIT tone usually when the number is unreachable.

 

Have you tried dialing the 3196880 number from a phone attached tot he same phone line and hearing what happens on the line?

 

Also, it looks like you have already asked the same question already here: http://voiceguide.com/forums/index.php?showtopic=5927

 

 

120224.221 6 1 state Dialing 3196880...

120224.772 3 1 ev Dialogic 135,TDX_SETHOOK, crn=2000000b, 0,0,0,DX_OFFHOOK,CALL_OUTBOUND,

120224.772 3 1 tqScr enq cmd_ScriptEventCode

120224.772 6 1 tqScr run cmd_ScriptEventCode TDX_SETHOOK, iActionID=0, crn=0[0|0|0|0|0][DX_OFFHOOK|CALL_OUTBOUND||||]

120224.772 6 1 ScriptEvent TDX_SETHOOK DX_OFFHOOK|CALL_OUTBOUND|

120224.772 6 1 LsWaitAfterDialingOut : 135,TDX_SETHOOK,0,0,0,DX_OFFHOOK,CALL_OUTBOUND,

120224.822 3 1 ev Dialogic 134,TDX_CST, crn=2000000b, 65535,0,0,DE_LCON,,

120224.822 3 1 tqScr enq cmd_ScriptEventCode

120224.822 6 1 tqScr run cmd_ScriptEventCode TDX_CST, iActionID=0, crn=0[65535|0|0|0|0][DE_LCON|||||]

120224.822 6 1 ScriptEvent TDX_CST DE_LCON||

120224.822 6 1 LsWaitAfterDialingOut : 134,TDX_CST,65535,0,0,DE_LCON,,

120227.336 3 1 ev Dialogic 133,TDX_CALLP, crn=2000000b, 11,0,0,CR_CEPT,,

120227.336 3 1 tqScr enq cmd_ScriptEventCode

120227.336 6 1 tqScr run cmd_ScriptEventCode TDX_CALLP, iActionID=0, crn=0[11|0|0|0|0][CR_CEPT|||||]

120227.336 6 1 ScriptEvent TDX_CALLP CR_CEPT||

120227.336 6 1 LsWaitAfterDialingOut : 133,TDX_CALLP,11,0,0,CR_CEPT,,

120227.336 6 1 dial OnOutboundCallAnswered begin [NotContacted_SitTone]

[Guest u4910]

Yes. I just tried calling from a phone plugged in that line and I don't hear any SIT tone and the call picks up fine.

Is there anything else I can try?

[Guest u4910]

It sounds like there may be some static sometimes on the line. How can I make it more tolerant of this if this is causing it to not dial out?

[Guest u4910]

I've added a second line, and the second line works better (not perfect) but it completes most calls. So it must be detecting some noise on the line. Is there a way to make it more tolerant of noise?

[SupportTeam]

In the current release of v7 once Dialogic's call progress reports that a SIT is detected the call will end.

 

Can you make an outbound call on the problem line using a script that just has a Record module in it, and in the Answering Machine script text box specify DISABLE

 

This will result in the script to start immediate after the call is made, and the record module will start recording what is heard on the line.

 

Then .ZIP up and post the sound file recorded by the record module. We'll then be able to hear what noise is causing the false SIT detection.

 

Another thing to try would be to swap the phone lines around to see if the problem is caused by the line, or if it is caused by the port on the Dialogic card.

[Guest u4910]

Thank you so much for the post about being able to record the call going out, this will help for sure.

It's working a little better now. I have moved the lines around some and maybe that reduced the noise. I can make calls on line one fine, but now if I try to use both at the same time, line two (meaning the #2 line on the card -- I've even switched the lines on the card with the same results.) gives a "silence path not defined".

I'll troubleshoot some more, but wanted to know what that means. When I listen to that particular wav file, I hear silence, then ringing and then a short silence at the end. So, the call is made, it rings once or so and then it hangs up before I can answer. No SIT tone or anything like that. (That's why I didn't post it.).

Thanks,

 

 

8 18 3 FindFullPathToScript_VgsOrVgp start [e:\ivr\outbound1\listen.vgs]

000314.358 18 LoadedVgs_Find e:\ivr\outbound1\listen.vgs at idx=2

000314.358 18 3 rvns add [scriptsPath]{e:\ivr\outbound1\}

000314.358 18 3 StartModuleDefault=[Record 2]

000314.358 18 3 t clear (force=False)

000314.368 18 3 RunModule start [Record,[Record 2],15]

000314.368 18 3 [Record 2] VGMTYPE_REC run start

000314.368 18 3 rv add [Record 2]{e:\ivr\outbound1\listen.wav}

000314.368 18 3 RecSoundStart [e:\ivr\outbound1\listen.wav] call beep=False

000314.368 18 3 state [Record 2] Recording e:\ivr\outbound1\listen.wav

000314.368 18 3 tqTel que cmd_SilenceDetectSet [30,10,0,0,0][||||]

000314.368 7 3 tqTel run cmd_SilenceDetectSet

000314.368 18 3 tqTel que cmd_RecordFileStart [6,0,0,0,0][||||]

000314.368 7 3 tqTel run cmd_RecordFileStart

000314.368 7 3 tqScr enq cmd_ScriptEventCode

000314.368 6 3 tqScr run cmd_ScriptEventCode EV_REC_FINISHED, iActionID=0, crn=0[996420|0|0|0|0][|||||]

000314.368 6 3 ScriptEvent EV_REC_FINISHED ||

000314.368 6 3 LsRecRecording EV_REC_FINISHED,EV_REC_FINISHED

000314.368 6 3 path {EV_REC_FINISHED} not found

000314.368 6 3 WARN rec complete event without rec reason being recieved first. Assume silence as the cause

000314.368 6 3 rv rec length: Record 2_RecLen100ms = 863970

000314.368 6 3 rv add [Record 2_RecLen100ms]{863970}

000314.368 6 3 rv add [Record 2_EndRecCause]{silence}

000314.368 6 3 path {silence} not found

000314.368 6 3 HangupCall ('and any associated'=False), source={silence} path not defined

000314.368 6 3 state Hanging up call... [{silence} path not defined]

000314.368 6 3 rv add [Hangup Source]{{silence} path not defined}

000314.368 6 3 RecSoundStop begin trunc100ms=0, sCaller=HangupCall_Main

000314.368 6 3 tqTel que cmd_RecordStop [0,0,0,0,0][||||]

000314.368 7 3 tqTel run cmd_RecordStop

000314.368 6 3 DropCall_ScriptRunStateAware start (crn=20000046)

000314.368 6 3 t set 1 EV_TIMEOUT_DELAY_ANALOG_DXDROP

000314.368 18 3 RecSoundStart [e:\ivr\outbound1\listen.wav] ok

000314.378 18 3 t set 3600 EV_TIMEOUT_RECMAXTIM

[SupportTeam]

Please post both the ktTel and vgEngine traces capturing system startup and the outgoing call, we can then see what happened on this call.