Disconnect

[mehdi_h]

sorry to come back with this subject but, I have diffuclties to detect that the called user has hanged_up. I have set the coorect data in the config xml file : 440Hz 500ms on, 500ms off and the system did not detet the hang up and still played the file.

 

thkx

0321vgm.txt

[mehdi_h]

please consider these files:

0321tw.txt

0321vgm.txt

Config.xml

[SupportTeam]

Can you please also post the recording of the disconnect tone.

[mehdi_h]

For your information I ave now set the diconnecttone to YES in the DCM. It seems that it sometime it detects hangup. could you please confirm regarding the log files.

 

tkx

0321tw.txt

0321vgm.txt

gol.wav

[SupportTeam]

From traces we see that this system does issue Loop Current Drop - so you should be getting pretty accurate end of call detection - but for some reason we do not always see loop current drop event in traces. This can be because the PBX/Switch is not doing loop current drop or the Dialogic card is not detecting it.

 

Setting DisconnectTone in DCM to YES does not affect anything. That just makes Dialogic drivers issue a 'disconnect tone was heard' event when loop current is detected. This setting was made for older systems which did not listen out for the loop current drop. VoiceGuide does listen for loop current drop event so this setting would not affect end of call detection.

 

The tone defections are in ConfigLine.xml, not in Config.xml. You added the tone definition to the wrong file.

You can see in "tw" trace what tone definitions are read in.

[mehdi_h]

ok have written in the correct file now. Please chekc the log file. It seems that The wav file is played until the end without taken into account the hangup

 

tkx

0322tw.txt

0322vgm.txt

[SupportTeam]

'tw' trace shows that the TID_DISCONNECT tone definition in ConfigLine.xml file is specifying 500Hz, and not 440Hz which is the frequency of the "ON" part of the disconnect tone which you recorded:

 

181211.046 tone ch id:TID_DISCONNECT:257, f1:500:50, f2:0:0, cad:50:5,50:5, count:3

 

You should change the tone definition to specify 440Hz.

 

Also I'd change the 'Count' setting to be 2.

[mehdi_h]

too stupid :-) should you please check if it is now ok . How can I chek that it is ok in the log files..?

 

tkx

0322vgm.txt

0322tw.txt

[SupportTeam]

Trace shows that all 3 calls ended as Dialogic detected Loop Current Drop on line. (the DE_LCOF event means 'Loop Current Drop'):

 

185723,11 1 tw DialogicEvent 134,TDX_CST,0,0,0,DE_LCOF,,

 

185742,80 1 tw DialogicEvent 134,TDX_CST,0,0,0,DE_LCOF,,

 

185758,80 1 tw DialogicEvent 134,TDX_CST,0,0,0,DE_LCOF,,

 

disconnect tone detection did not play a role here.

 

'tw' trace did not include startup of VG phase so we could not see what tone definitions were loaded.

 

Have a look in the 'tw' trace just after startup, the tone definition reporting section is pretty easy to identify.

[mehdi_h]

the tone have nothing to do here because "Loop Current Drop" has the priority ?

 

tkx

[SupportTeam]

The Dialogic card has indicated that Loop Current Drop was detected on the line.

 

It's not really question of priority as such. A Switch/PBX will usually do one or the other only.

ie: at end of call it will either only do a loop current drop or only play a disconnect tone.

 

Having Switch/PBX setup to do Loop Current Drop all the time is preferred as detection of loop current drop is pretty much 100% reliable, whereas tone detection is not always 100% reliable.