Issabel ISO (Latest): Download Here
Cloud Services: User Portal - Quick Guide
News: Telegram channel
Become a Patron!
  • GeneralDev
  • Recording is missing when using Queue Continue Destination

I've tried to use the new feature Queue Continue Destination but when I used it all the queue recordings transferred to the new Queue Continue Destination are missing

Can any one help ?

    a month later

    Hi, I have the same problem, after set any option in "Queue Continue Destination", records are deleted after extension hangup.
    The Issabel run the macro [sub-record-cancel] in extensions_additional.conf
    The Issabel run "rm -f" in file audio in the /var/spool/asterisk/monitor/

    [2019-03-29 09:01:26] VERBOSE[17344][C-0001665f] app_mixmonitor.c: == MixMonitor close filestream (mixed)
    [2019-03-29 09:01:26] VERBOSE[17344][C-0001665f] pbx.c: -- Executing [s@sub-record-cancel:4] Set("SIP/TKCIOSP-00019948", "REC_STATUS=") in new stack
    [2019-03-29 09:01:26] VERBOSE[17344][C-0001665f] pbx.c: -- Executing [s@sub-record-cancel:5] Set("SIP/TKCIOSP-00019948", "MON_BASE=/var/spool/asterisk/monitor/2019/03/29/") in new stack
    [2019-03-29 09:01:26] VERBOSE[17344][C-0001665f] pbx.c: -- Executing [s@sub-record-cancel:6] Set("SIP/TKCIOSP-00019948", "
    MON_FMT=gsm") in new stack
    [2019-03-29 09:01:26] VERBOSE[17344][C-0001665f] pbx.c: -- Executing [s@sub-record-cancel:7] ExecIf("SIP/TKCIOSP-00019948", "50?System(rm -f /var/spool/asterisk/monitor/2019/03/29/q-1-084988580196-20190329-090043-1553860843.196420.gsm)") in new stack
    [2019-03-29 09:01:27] VERBOSE[17389][C-0001665f] app_mixmonitor.c: == End MixMonitor Recording SIP/TKCIOSP-00019948

    Any solution?
    This is a bug?

    Thanks.

      3 months later

      Try replace this context this new one.

      [sub-record-cancel]
      include => sub-record-cancel-custom
      exten => s,1,Set(__REC_POLICY_MODE=${REC_POLICY_MODE_SAVE})
      exten => s,n,ExecIf($["${REC_STATUS}"!="RECORDING"]?Return())
      exten => s,n,StopMixMonitor()
      exten => s,n,Return()

      If work fine , you have to do something for not lost this new configuration at the next "reload config"

        if you add this context to file : extensions_custom.conf
        will replace original, and you will not lost recording files.
        Maybe, the functionality of recording "on demand" mode may stop working, and record the audio anyway.
        But it is not a priority for me.
        I need all recording files as a priority.

          I've tried it but still the Queue recording is yes and when the extensions hangs up and the call is diverted for an announcement, the the recordings of these calls are missing

          Is there anything else that I can do?

            tarekkoura Please show me your console logs , to see what is happen.
            If you look at "for example" Emiliano logs, you could see that Asterisk execute
            " Executing [s@sub-record-cancel:7] ExecIf("SIP/TKCIOSP-00019948", "50?System(rm -f /var/spool/asterisk/monitor/2019/03/29/q-"
            This mean a call to command rm (remove) of the OS.
            If you have replace the context [sub-record-cancel] at extensions_additional, Asterisk will not remove this audio file.
            Please check and see.
            The other instance that asterisk call this subroutine if when call is too short. , so it remove audio files that not have the minimum duration.

              Solved
              Thanks very much for the help <3

                as Schiesa suggested:

                go to
                /etc/asterisk/extensions_additional.conf

                and change [sub-record-cancel]

                from:

                [sub-record-cancel]
                include => sub-record-cancel-custom
                exten => s,1,Set(REC_POLICY_MODE=${REC_POLICY_MODE_SAVE})
                exten => s,n,ExecIf($["${REC_STATUS}"!="RECORDING"]?Return())
                exten => s,n,StopMixMonitor()
                exten => s,n,Set(
                REC_STATUS=)
                exten => s,n,Set(MON_BASE=${IF($[${LEN(${MIXMON_DIR})}]?${MIXMON_DIR}:${ASTSPOOLDIR}/monitor/)}${YEAR}/${MONTH}/${DAY}/)
                exten => s,n,Set(MON_FMT=${IF($[${LEN(${MIXMON_FORMAT})}]?${IF($["${MIXMON_FORMAT}"="wav49"]?WAV:${MIXMON_FORMAT})}:wav)})
                exten => s,n,ExecIf($[${LEN(${CALLFILENAME})} & ${STAT(f,${MON_BASE}${CALLFILENAME}.${MON_FMT})}]?System(rm -f ${MON_BASE}${CALLFILENAME}.${MON_FMT}))
                exten => s,n,Set(
                CALLFILENAME=)
                exten => s,n,Set(CDR(recordingfile)=)
                exten => s,n,Return()

                ;--== end of [sub-record-cancel] ==--;

                to:

                [sub-record-cancel]

                ;--== end of [sub-record-cancel] ==--;

                  Correction:

                  go to

                  /etc/asterisk/extensions_override_issabelpbx.conf

                  add:

                  [sub-record-cancel]
                  include => sub-record-cancel-custom
                  exten => s,1,Set(__REC_POLICY_MODE=${REC_POLICY_MODE_SAVE})
                  exten => s,n,ExecIf($["${REC_STATUS}"!="RECORDING"]?Return())
                  exten => s,n,StopMixMonitor()
                  exten => s,n,Return()

                  ;--== end of [sub-record-cancel] ==--;

                  2 months later

                  tarekkoura that is great,
                  We should report it as BUG on github,

                    2 months later

                    tarekkoura

                    Thank you for this solution. I was having this same issue "Recording Missing" through the GUI and it worked just fine after creating/updating the file "/etc/asterisk/extensions_override_issabelpbx.conf"

                      Write a Reply...