[asterisk-bugs] [JIRA] (ASTERISK-23381) ChanSpy- Barge only works on the initial 'spy', if the spied-on channel makes a new call, unable to barge.

[Rusty Newton (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-23381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-23381:
------------------------------------

    Assignee: Robert Moss
      Status: Waiting for Feedback  (was: Triage)
    
> ChanSpy- Barge only works on the initial 'spy', if the spied-on channel makes a new call, unable to barge.
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-23381
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23381
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_chanspy
>    Affects Versions: 11.6.0, 11.7.0
>         Environment: CentOS 6.5, asterisk 11.7.0
>            Reporter: Robert Moss
>            Assignee: Robert Moss
>            Severity: Minor
>
> When barging, our monitors can use either a prefix, or the full extension to monitor a channel. Once the agent hangs up, they are still monitoring. 
> When a new call is connected to the monitor, listen+whisper still work, however barging does not. Only the spied-on agent can hear the monitor.
> This happens both when monitoring a single channel, and when monitoring a group of channels, as soon as the initially monitored call closes, they are unable to barge on subsequent monitors. 
> The workaround is to hangup and redial that monitor extension and then barge, which works fine so long as it's the first call being barged.

--
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