[asterisk-bugs] [JIRA] (ASTERISK-21722) chan motif behaves wrong

[Private Name (JIRA)]

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

Private Name commented on ASTERISK-21722:
-----------------------------------------

I invite the engineers to connect to my server directly, while I place a call, and watch the issue. But there is a worse issue with chan_motif. This channel opens a file called /tmp/refs. This file grows unlimitedly and forever, until it reaches several gigs and then Asterisk must be stopped and the file erased. My virtual machines routinely run out of space. That is very traumatic for me. I wish to ask the honorable engineers if there is a workaround for the file issue, or if it is safe to use a Linux command like "truncate file --size=0".
The original issue of the Motif channel is that when the call is initiated with "originate", the Dial command continues, does not remain waiting for the call to close. But the call is well and alive.  
                
> chan motif behaves wrong
> ------------------------
>
>                 Key: ASTERISK-21722
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21722
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_motif
>    Affects Versions: 11.3.0
>         Environment: linux 6.1 redhat
>            Reporter: Private Name
>         Attachments: asterisk.txt
>
>
> I am uploading a debug trace. Basically, when my dialer places a call with originate, using chan_local, and then Motif,the channel "thinks" the calls if finished and executes the hangup handler. But the calls is live and well and it can last for hours.
> I know it is weird, but I have the trace and I can reproduce it. 
> The dialer sees the call as Answered on the far end (Motif) and then dials another leg via the same "Local" channel, and I play music on hold.

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