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

[Matt Jordan (JIRA)]

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

Matt Jordan edited comment on ASTERISK-21722 at 5/18/13 11:30 AM:
------------------------------------------------------------------

Several things here.

# The /tmp/refs issue is a bug that was filed under ASTERISK-21785, and was fixed in r388700. It is not yet in a release candidates or a tagged release, but should be in the next RC.
# The issue has not been filed correctly. The instructions linked here by Rusty describe the information that should be provided in an issue.
# The DEBUG log was not generated correctly. When filing issues, please follow the instructions linked here by Rusty.
# This is not a support forum. If you need support, there are multiple ways to get support from the developer community. If you need someone to connect to your machine and provide support, contact the {{asterisk-biz}} mailing list. There are plenty of open source developers who will be willing to provide support for Asterisk.

All of that being said, I'm going to make a few guesses here based on your incomplete log file. *These are guesses. Your log file does not show all of the information needed.*

{noformat}
[Apr 29 10:11:47] DEBUG[9054][C-00002e7d]: channel.c:2661 ast_softhangup_nolock: Soft-Hanging up channel 'Local/19544447408 at onsite-0000335e;2'
[Apr 29 10:11:47] DEBUG[9054][C-00002e7d]: app_stack.c:578 gosub_exec: Channel Local/19544447408 at onsite-0000335e;2 has no datastore, so we're allocating one.
[Apr 29 10:11:47] DEBUG[9054][C-00002e7d]: app_stack.c:620 gosub_exec: Setting 'ARG1' to 'args'
{noformat}

The Local channel was hung up, most likely due to a local channel optimization. The next arguments indicate that some GoSub routine was executed on the Local channel's {{;2}} channel. Since hangup handlers are a type of GoSub routine, I'm guessing this is the hangup handler.

Assuming this is correct, then:

The hangup handler was not executed on the Motif channel. It was executed on the Local channel because the Local channel hung up, and because you put the hangup handler on the Local channel instead of the Motif channel. This is a configuration issue and not a bug.
                
      was (Author: mjordan):
    Several things here.

# The /tmp/refs issue is a bug that was filed under ASTERISK-21785, and was fixed in r388700. It is not yet in a release candidates or a tagged release, but should be in the next RC.
# The issue has not been filed correctly. The instructions linked here by Rusty describe the information that should be provided in an issue.
# The DEBUG log was not generated correctly. When filing issues, please follow the instructions linked here by Rusty.
# This is not a support forum. If you need support, there are multiple ways to get support from the developer community.

All of that being said, I'm going to make a few guesses here based on your incomplete log file. *These are guesses. Your log file does not show all of the information needed.*

{noformat}
[Apr 29 10:11:47] DEBUG[9054][C-00002e7d]: channel.c:2661 ast_softhangup_nolock: Soft-Hanging up channel 'Local/19544447408 at onsite-0000335e;2'
[Apr 29 10:11:47] DEBUG[9054][C-00002e7d]: app_stack.c:578 gosub_exec: Channel Local/19544447408 at onsite-0000335e;2 has no datastore, so we're allocating one.
[Apr 29 10:11:47] DEBUG[9054][C-00002e7d]: app_stack.c:620 gosub_exec: Setting 'ARG1' to 'args'
{noformat}

The Local channel was hung up, most likely due to a local channel optimization. The next arguments indicate that some GoSub routine was executed on the Local channel's {{;2}} channel. Since hangup handlers are a type of GoSub routine, I'm guessing this is the hangup handler.

Assuming this is correct, then:

The hangup handler was not executed on the Motif channel. It was executed on the Local channel because the Local channel hung up, and because you put the hangup handler on the Local channel instead of the Motif channel. This is a configuration issue and not a bug.
                  
> 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