[asterisk-bugs] [JIRA] (ASTERISK-21298) Confbridge recording fails

[Brad Belanger (JIRA)]

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

Brad Belanger updated ASTERISK-21298:
-------------------------------------

          Description: 
Confbridge recording produces a mangled file name after restarting recording during a call. After calling stop the second time it automatically starts another recording with the same uid that stops immediately. Any further attempts to start/stop recording fails with no respons
e on the console. 

ccc-voip-dev*CLI> confbridge record start 1
Recording started
  == Begin MixMonitor Recording ConfBridgeRecorder/conf-1-uid-72230577
ccc-voip-dev*CLI> 
ccc-voip-dev*CLI> confbridge record stop 1
Recording stopped.
  == MixMonitor close filestream (mixed)
ccc-voip-dev*CLI> 
ccc-voip-dev*CLI> 
ccc-voip-dev*CLI> confbridge record start 1
Recording started
  == Begin MixMonitor Recording ConfBridgeRecorder/conf-1-uid-1936058528
ccc-voip-dev*CLI> 
ccc-voip-dev*CLI> confbridge record stop 1
Recording stopped.
  == MixMonitor close filestream (mixed)
  == Begin MixMonitor Recording ConfBridgeRecorder/conf-1-uid-1936058528
ccc-voip-dev*CLI> 
ccc-voip-dev*CLI> confbridge record stop 1
Recording could not be stopped.
ccc-voip-dev*CLI> confbridge record start 1
ccc-voip-dev*CLI> 
ccc-voip-dev*CLI> confbridge record stop 1
ccc-voip-dev*CLI> 

Files produced by these start/stops
282924 Mar 18 16:08 confbridge-1-1363637319.wav
347564 Mar 18 16:09 confbridge-1-1363637319.wavconfbridge-1-1363637350.wav
44 Mar 18 16:09 confbridge-1-1363637372.wav

Once it reaches this state new calls fail and an Adhearsion app starts getting timeouts connecting to the manager.

Note - this issue appears to be resolved in trunk.

  was:
Confbridge recording produces a mangled file name after restarting recording during a call. After calling stop the second time it automatically starts another recording with the same uid that stops immediately. Any further attempts to start/stop recording fails with no respons
e on the console. 

ccc-voip-dev*CLI> confbridge record start 1
Recording started
  == Begin MixMonitor Recording ConfBridgeRecorder/conf-1-uid-72230577
ccc-voip-dev*CLI> 
ccc-voip-dev*CLI> confbridge record stop 1
Recording stopped.
  == MixMonitor close filestream (mixed)
ccc-voip-dev*CLI> 
ccc-voip-dev*CLI> 
ccc-voip-dev*CLI> confbridge record start 1
Recording started
  == Begin MixMonitor Recording ConfBridgeRecorder/conf-1-uid-1936058528
ccc-voip-dev*CLI> 
ccc-voip-dev*CLI> confbridge record stop 1
Recording stopped.
  == MixMonitor close filestream (mixed)
  == Begin MixMonitor Recording ConfBridgeRecorder/conf-1-uid-1936058528
ccc-voip-dev*CLI> 
ccc-voip-dev*CLI> confbridge record stop 1
Recording could not be stopped.
ccc-voip-dev*CLI> confbridge record start 1
ccc-voip-dev*CLI> 
ccc-voip-dev*CLI> confbridge record stop 1
ccc-voip-dev*CLI> 

Files produced by these start/stops
282924 Mar 18 16:08 confbridge-1-1363637319.wav
347564 Mar 18 16:09 confbridge-1-1363637319.wavconfbridge-1-1363637350.wav
44 Mar 18 16:09 confbridge-1-1363637372.wav

Once it reaches this state new calls fail and an Adhearsion app starts getting timeouts connecting to the manager.


    Affects Version/s: 11.3.0
    
> Confbridge recording fails
> --------------------------
>
>                 Key: ASTERISK-21298
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21298
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_confbridge
>    Affects Versions: 11.2.1, 11.3.0
>         Environment: CentOS 6.3 x86_64 VM under ESX5
>            Reporter: Brad Belanger
>
> Confbridge recording produces a mangled file name after restarting recording during a call. After calling stop the second time it automatically starts another recording with the same uid that stops immediately. Any further attempts to start/stop recording fails with no respons
> e on the console. 
> ccc-voip-dev*CLI> confbridge record start 1
> Recording started
>   == Begin MixMonitor Recording ConfBridgeRecorder/conf-1-uid-72230577
> ccc-voip-dev*CLI> 
> ccc-voip-dev*CLI> confbridge record stop 1
> Recording stopped.
>   == MixMonitor close filestream (mixed)
> ccc-voip-dev*CLI> 
> ccc-voip-dev*CLI> 
> ccc-voip-dev*CLI> confbridge record start 1
> Recording started
>   == Begin MixMonitor Recording ConfBridgeRecorder/conf-1-uid-1936058528
> ccc-voip-dev*CLI> 
> ccc-voip-dev*CLI> confbridge record stop 1
> Recording stopped.
>   == MixMonitor close filestream (mixed)
>   == Begin MixMonitor Recording ConfBridgeRecorder/conf-1-uid-1936058528
> ccc-voip-dev*CLI> 
> ccc-voip-dev*CLI> confbridge record stop 1
> Recording could not be stopped.
> ccc-voip-dev*CLI> confbridge record start 1
> ccc-voip-dev*CLI> 
> ccc-voip-dev*CLI> confbridge record stop 1
> ccc-voip-dev*CLI> 
> Files produced by these start/stops
> 282924 Mar 18 16:08 confbridge-1-1363637319.wav
> 347564 Mar 18 16:09 confbridge-1-1363637319.wavconfbridge-1-1363637350.wav
> 44 Mar 18 16:09 confbridge-1-1363637372.wav
> Once it reaches this state new calls fail and an Adhearsion app starts getting timeouts connecting to the manager.
> Note - this issue appears to be resolved in trunk.

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