[asterisk-bugs] [JIRA] (ASTERISK-22661) Unable to exit ChanSpy if spied channel does not have a call in progress

[Chris Hillman (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-22661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210885#comment-210885 ] 

Chris Hillman commented on ASTERISK-22661:
------------------------------------------

Thank you Michael, I have tried it with numeric DTMF digits and the behavior is the same. Just tested with x(6). We need to be able to specify an extension to observe. In production this will be spanning about 260 extensions and cycling between all of them will be unpractical.
                
> Unable to exit ChanSpy if spied channel does not have a call in progress
> ------------------------------------------------------------------------
>
>                 Key: ASTERISK-22661
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22661
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_chanspy
>    Affects Versions: 1.8.23.1
>         Environment: Running Asterisk Version = 1.8.23.1  on CentOS release 6.4 Kernel  2.6.32-358.6.2.el6.i686 - 32 Bit 
>            Reporter: Chris Hillman
>            Assignee: Chris Hillman
>         Attachments: debug_output.txt, dialplan_example.txt, issue_22661_full_log
>
>
> I have a context in the dialplan where I want to be able to ChanSpy on SIP/361-SIP/364, and use the 'x' option to exit the ChanSpy application and select a new Channel to spy on. If the Channel I'm spying on is not in a call I can not exit the ChanSpy application.
> I have attached my dialplan code as well as console verbose output and SIP debug info.
> Option I'm trying to use:
>     x(digit):
>     digit - Specify a DTMF digit that can be used to exit the application.
> The digit will not be recognized if the spied party is not in a call at the time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira