[asterisk-bugs] [JIRA] (ASTERISK-24536) AMI redirect with PJSIP fails to move extra channel

Mark Michelson (JIRA) noreply at issues.asterisk.org
Mon Dec 15 15:37:29 CST 2014


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

Mark Michelson commented on ASTERISK-24536:
-------------------------------------------

I have not been able to reproduce this problem yet. Here is my test extensions.conf file:

{panel: title=extensions.conf}
{noformat: nopanel=true}
[default]
exten => _2xx,1,NoOp()
same => n, Dial(PJSIP/${EXTEN},,tT)

exten => 306,1,Answer()
same => n,Playback(demo-congrats)
same => n,Hangup()
{noformat}
{panel}

I place a call from PJSIP/200 to PJSIP/201 by dialing 201. I have the "tT" in the Dial() to force a basic bridge since that's what appears in your logs. I then issue a redirect like the following:

{noformat}
action: redirect
channel: PJSIP/200-00000000
exten: 306
context: default
priority: 1
extrachannel: PJSIP/201-00000001
extraexten: 306
extracontext: default
extrapriority: 1
{noformat}

Both phones are succesfully redirected to {{306 at default}}. I've tried the test about 20 times and it has been successful every time. I suspect there is either a difference in
A) The way that you are establishing the initial bridge. I use the Dial() application. Are you doing it some other way? Originate? The Bridge() application? Since you filled in the choice that this issue happens constantly, I suspect that this may be where our setups differ.
B) The load on the system. When I run my test, it's the only call in the entire Asterisk system. I suspect that if there is a race condition, and you're using a more heavily-loaded system, you may see the issue more frequently than me. However, that would not necessarily contribute towards the issue happening constantly.

> AMI redirect with PJSIP fails to move extra channel
> ---------------------------------------------------
>
>                 Key: ASTERISK-24536
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24536
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip, Core/Bridging, Core/ManagerInterface
>    Affects Versions: 13.0.0
>            Reporter: Niklas Larsson
>            Assignee: Mark Michelson
>         Attachments: redirect.txt
>
>
> We have one softmix with one or two PJSIP channels in. Then we are sending an AMI action:
> {quote}
> action: Redirect
> actionid: 1416320876.9306
> channel: PJSIP/tjoho-00000044
> exten: moh
> context: hold-bridge
> priority: 1
> extrachannel: PJSIP/wid3-00000045
> extraexten: moh
> extracontext: hold-bridge
> extrapriority: 1
> {quote}
> Result: the first channel is placed in hold-bridge,moh,1 but the second is hunged up.
> {noformat}
> [Nov 18 15:26:47] WARNING[1370]: channel.c:10376 ast_channel_move: Can't move channel. One or both is dead (Surrogate/PJSIP/wid3-00000045 <-- PJSIP/wid3-00000045)
> [Nov 18 15:26:47] WARNING[1370]: pbx.c:9687 ast_async_goto: Unable to gain control of channel PJSIP/wid3-00000045
> [Nov 18 15:26:47] ERROR[1370]: utils.c:1449 ast_careful_fwrite: fwrite() returned error: Broken pipe
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list