Guest DiegoBellini Report post Posted 10/14/2009 06:33 PM I have an IVR working one year ago without problems, but it he does little less than 1 month he start to giving this error. Scarcely it Begins to work the call is fallen in abrupt form, without asking any information to the user, and without apparent motive. logs.zip Share this post Link to post
SupportTeam Report post Posted 10/14/2009 07:18 PM Trace shows that VoiceGuide hung up the call as the Dialogic card reported hearing the DISCONNECT_TAPI1 tone on the line. You should edit the ConfigLine.xml file's DISCONNECT_TAPI1 entry to make that tone less likely to be mistakenly detected. Usually setting the 'Count' field in the Tone definition entry to a higher number (5 or more) fixes this. Or just delete that tone definition entry altogether if you want. 143215.120 18 3 ev Dialogic 134,TDX_CST, crn=10000001, 1009,0,0,DE_TONEON,DISCONNECT_TAPI1, 143215.120 0176 003 ev TDX_CST (CST Event Received) 143215.120 0176 003 TDX_CST DE_TONEON cst_data=1009 143215.120 0176 003 tone description retrieve hli=088B0048, iToneUserID[1]=1009 sToneUserName[1]=[DISCONNECT_TAPI1] 143215.120 0176 003 raise Dialogic TDX_CST 134 (1009 0 0 DE_TONEON DISCONNECT_TAPI1 ) Share this post Link to post
