| Summary: | ASTERISK-17450: busydetect not detecting some patterns | ||
| Reporter: | Sebastian Gutierrez (sum) | Labels: | |
| Date Opened: | 2011-02-21 10:17:54.000-0600 | Date Closed: | 2011-06-07 14:05:02 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_dahdi |
| Versions: | 1.6.2.15 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Chandahdi: busydetect=yes, busycount=2 Indications zone = us, with the modifications for my country for busy: 425Hz Pattern(0.2ms on, 0.2ms off, 0.2ms on, 0.6ms off) indications.conf [us] ..... busy = 425/200,0/200,425/200,0/600 I compiled with BUSY DETECT DEBUG. I can see: [Feb 10 15:48:06] DEBUG[26968]: dsp.c:1276 ast_dsp_busydetect: busy detector: FAILED with avgtone: 255, avgsilence 30 [Feb 10 15:48:06] DEBUG[26968]: dsp.c:1276 ast_dsp_busydetect: busy detector: FAILED with avgtone: 255, avgsilence 30 [Feb 10 15:48:06] DEBUG[26968]: dsp.c:1276 ast_dsp_busydetect: busy detector: FAILED with avgtone: 255, avgsilence 30 [Feb 10 15:48:40] DEBUG[26971]: dsp.c:1276 ast_dsp_busydetect: busy detector: FAILED with avgtone: 260, avgsilence 30 [Feb 10 15:48:40] DEBUG[26971]: dsp.c:1276 ast_dsp_busydetect: busy detector: FAILED with avgtone: 260, avgsilence 30 And when I hangup the line nothing more is shown of the busydetect debug, but the line is still on. I'm not sure if I'm missing something about the busy detector | ||
| Comments: | By: Sebastian Gutierrez (sum) 2011-04-06 08:49:04 the busy detect works fine on asterisk 1.4.4 with zaptel using zone br By: cmaj (cmaj) 2011-04-26 23:16:12 indications.conf is for playing back tones, not listening for them. By: Jonathan Rose (jrose) 2011-04-27 10:15:17 "busy = 425/200,0/200,425/200,0/600" 4-length pattern busy cadence detection is only a feature in trunk. And you don't set them in indications.conf, you set a busypattern in chan_dahdi.conf and use busydetect=yes By: Sebastian Gutierrez (sum) 2011-04-27 10:18:13 I also set this on indications (so forget about indications) and busydetect=yes, and busypattern, is only supported in trunk? why zaptel and asterisk 1.4 detected the pattern fine? By: Jonathan Rose (jrose) 2011-04-27 10:20:30 Closing issue since this isn't a feature of this version of Asterisk. busydetect and busypattern are in more than trunk but in builds prior to trunk, you can only use something like... busydetect=X,Y whereas in trunk it can be set like busydetect=X1,Y1,X2,Y2 As for why it's working in 1.4, no idea. It's not supposed to be able to detect odd busy patterns like that. Maybe 1.4 uses a different means of checking. Regardless, we are only doing security fixes for 1.4 and 1.6.2 now. By: Sebastian Gutierrez (sum) 2012-05-03 11:07:19.426-0500 in 1.8.12 is possible to use this kind of patterns??? | ||