VoiceGuide IVR Software Main Page
Jump to content

Disconnect

Recommended Posts

Sorry but this subject drives me crazy.

I have problems again on disconnect detection using & D/41PCI. through PBX so to make sure that this is not linked with the PBX I have tried using direct analog line.

 

Please find all the log files attached of course I have put the right values in the xml file but it seems that dialogic is waiting for à loop drop off and this seems to come later after the hang up.

 

Could you pleas help me analysing the log files and help me in my reccurent problem.

Share this post


Link to post

Trace shows that the Dialogic card detected a loop current drop on the line about 15 seconds after module [ecouter] started playing. System hung up when the loop current drop was reported.

 

It all seems fine and as expected, what is the problem?

 

 

123857,03 1 state [ecouter] Playing

123857,05 1 state [ecouter] Playing (C:\gol2.wav)

123857,05 1 timer clear

123857,06 1 play start ok, lPlayId=921125

123911,88 1 tw DialogicEvent 134,TDX_CST,0,0,0,DE_LCOF,,

123911,88 1 event DE_LCOF, iCode=134 state=1100

123911,88 1 LsPlayMsg EV_UNKNOWN_134,DE_LCOF

123911,89 1 path {DE_LCOF} not found

123911,89 1 HangupCall start (Loop Current Off (non-xfer vgm))

123911,89 1 rv add [Hangup Time]{24/04/2007 12:39:11}

Share this post


Link to post

My point is that 15s (how do you calculate that ?) is too much (maybe provider dependant) and I would expect the system to detect the disconnect tones to detect hang-up earlier. Otherwise I dont'understand why we have to specify the disconnect tones ..

 

 

 

Thkx

Share this post


Link to post

So you hung up the call at the time when the [ecouter] module started playing?

 

Instead of a Play module try using a Record mofule to record what tones are played on the line after hangup, then see if those tones match what is specified in ConfigLine.xml file.

 

(how do you calculate that ?)

the "123857,03" in "123857,03 1 state [ecouter] Playing" is a timestamp, read it as: 12:38:57.03

...

the "123911,88" in "123911,88 1 tw DialogicEvent 134,TDX_CST,0,0,0,DE_LCOF,," is a timestamp, read it as 12:39:11.88

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
×