| Summary: | ASTERISK-12015: app_chanspy group still broken in 1.4.19.2 | ||
| Reporter: | Steve Rawlings (stever28) | Labels: | |
| Date Opened: | 2008-05-14 06:27:11 | Date Closed: | 2008-05-14 09:11:34 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_chanspy |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | See also bug 0012461 CentOS 4.4, Asterisk 1.4.19.2, Zaptel 1.4.10.1, libpri 1.4.4, asterisk-addons 1.4.6. Just upgraded Asterisk, Zaptel and libpri to latest release and the error reported in bug 0012461 still remains. Our dialplan puts certain calls into spygroup 2000, these can then spied on by users with suitable access. However, when dialling the access code, 596 in our case, with the dialplan as shown below, no active calls in spygroup 2000 are spied on. If however I change the dialplan to read as follows - exten => 596,n,ChanSpy(|b) then calls are spied on with channel announcement. Unfortunately this allows spying of all calls, including those not in spygroup 2000. This worked fine in Asterisk 1.4.18 with the dialplan as below. ****** ADDITIONAL INFORMATION ****** exten => _8X.,1,Set(SPYGROUP=2000) exten => _8X.,n,NoOp(${SPYGROUP}) exten => _8X.,n,Dial(Zap/g2/${EXTEN:1}) exten => _8X.,n,Congestion exten => _8X.,n,Busy exten => 596,1,ringing exten => 596,n,Wait(1) exten => 596,n,ChanSpy(|g(2000)) exten => 596,n,Hangup | ||
| Comments: | By: Russell Bryant (russell) 2008-05-14 09:11:32 That fix will be included in 1.4.20. | ||