VoiceGuide IVR Software Main Page
Jump to content

Busy Event In Vg For Dialogic

Recommended Posts

Ever since switching to VG for Dialogic, VG doesn't seem to recognize 'busy' events. Is this the case, or am I missing something?

Share this post


Link to post

My tone definition, I believe, is properly resulting in a 'CR_BUSY' event. My 'OutDial_Result' variable however, is returning 'Uncontactable_NoAnswer'. Before I switched to VG for Dialogic, the 'OutDial_Result' variable would correspondingly return 'Uncontactable_Busy'.

 

112220.74 3 timer set 30 EV_TIMEOUT_MAKECALL_NORESPONSE

112221.27 3 tw DialogicEvent 135,TDX_SETHOOK,0,0,0,DX_OFFHOOK,CALL_OUTBOUND,

112221.28 3 event TDX_SETHOOK, iCode=135 state=5200

112221.29 3 LsWaitAfterDialingOut : 135,TDX_SETHOOK,0,0,0,DX_OFFHOOK,CALL_OUTBOUND,

112221.48 3 tw DialogicEvent 134,TDX_CST,425,0,0,DE_LCON,,

112221.48 3 event TDX_CST, iCode=134 state=5200

112221.49 3 LsWaitAfterDialingOut : 134,TDX_CST,425,0,0,DE_LCON,,

112231.25 3 tw DialogicEvent 133,TDX_CALLP,7,0,0,CR_BUSY,,

112231.27 3 event BUSY, iCode=133 state=5200

112231.27 3 LsWaitAfterDialingOut : 133,BUSY,7,0,0,CR_BUSY,,

112231.27 3 event CR_BUSY, iCode=133 state=5200

112231.29 3 LsWaitAfterDialingOut : 133,CR_BUSY,7,0,0,,,

112231.29 3 event TDX_CALLP, iCode=133 state=5200

112231.29 3 LsWaitAfterDialingOut : 133,TDX_CALLP,7,0,0,CR_BUSY,,

112231.29 3 DialoutProcessFailedDial start sCalledFrom=[LsWaitAfterDialingOut-CR_BUSY] RetriesLeft=0

112231.30 0 dial callque delete id=4295 (MSAccess)

112231.31 3 rvns add [OutDial_Result]{Uncontactable_NoAnswer}

 

Thanks,

Jack

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×