|Summary:||ASTERISK-00458: -DBUSYDETECT_TONEONLY AND -DBUSYDETECT_COMPARE_TONE_AND_SILENCE|
|Reporter:||Sergio Serrano (srsergio)||Labels:|
|Date Opened:||2003-10-30 02:00:25.000-0600||Date Closed:||2011-06-07 14:05:15|
|Description:||When I compile asterisk with -DBUSYDETECT_TONEONLY flag and busydetect=yes,busycount=6 and callprogress=yes asterisk detects X100P hungup correctly but it hung up during a conversation randomly. When I compile asterisk with |
-DBUSYDETECT_COMPARE_TONE_AND_SILENCE AND busydetect=yes, busycount=6 and callprogress = no asterisk doesn´t detect hungup properly but conversation doesn't crash.
****** ADDITIONAL INFORMATION ******
Our PBX is in Spain.
I use -DBUSYDETECT_MARTIN flag
|Comments:||By: x martinp (martinp) 2003-11-05 11:26:43.000-0600|
If you have the busy tone of the same length of pause and the signal just use DBUSYDETECT_MARTIN. If the busy tone has some inconsistency .. that is 200 ms of tone, 200 ms of pause (times 3) and then the pause is longer or shorter then you need to use DBUSYDETECT_MARTIN with -DBUSYDETECT_TONEONLY. You also shouldn't use callprogress since it's optimised for US. Also this flag -DBUSYDETECT_COMPARE_TONE_AND_SILENCE is to be used if you have too many false hangups but you could as well use this and busycount=10 (imagine that you press redial button while in the call and you transmit 10 DTMFS that sound to the algorithm like a busy tone ....)
Some guys were able to use it in Spain ...