[asterisk-bugs] [JIRA] (ASTERISK-20607) CLONE - [Regression] Confbridge recording does not work

[Jonathan Rose (JIRA)]

Jonathan Rose created ASTERISK-20607:
----------------------------------------

             Summary: CLONE - [Regression] Confbridge recording does not work
                 Key: ASTERISK-20607
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20607
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
    Affects Versions: 10.10.0, 11.0.0-beta2
            Reporter: Jonathan Rose


Confbridge recording does not work neither through CLI nor AMI.

confbridge.conf
===============

[conf_user]
type=user
music_on_hold_class=default
quiet=no
denoise=yes
announce_join_leave=no

[conf_bridge]
type=bridge
max_members=5
sound_join
sound_leave

extensions.conf
===============

exten => 3000,1,ConfBridge(3000,conf_bridge,conf_user)

Asterisk CLI
============

confbridge list 3000

Channel                       User Profile     Bridge Profile   Menu             CallerID
============================= ================ ================ ================ ================
SIP/toLab106-00000000         conf_userq conf_bridge                 <unknown>
SIP/toLab106-00000001         conf_userq conf_bridge                 <unknown>

LAB105*CLI> confbridge record start 3000
Recording started

LAB105*CLI> confbridge record stop 3000
Recording could not be stopped.

LAB105*CLI> core show channels
Channel              Location             State   Application(Data)
SIP/toLab106-0000000 3000 at InVADEDialler:1 Up      ConfBridge(3000,conf_bri
SIP/toLab106-0000000 3000 at InVADEDialler:1 Up      ConfBridge(3000,conf_bri
ConfBridgeRecorder/c s at default:1          Up      (None)

AMI
===

Action: ConfbridgeStartRecord
Conference: 3000

Response: Success
Message: Conference Recording Started.

Action: ConfbridgeStopRecord
Conference: 3000

Response: Error
Message: Internal error while stopping recording.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira