[asterisk-bugs] [JIRA] Updated: (ASTERISK-19985) Bridge - not always returning to the right context, priority, extension as it should.

[Matt Jordan (JIRA)]

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

Matt Jordan updated ASTERISK-19985:
-----------------------------------

    Target Release Version/s: 1.8.15.0

> Bridge - not always returning to the right context,priority,extension as it should.
> -----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-19985
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19985
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.13.0
>            Reporter: Maciej Krajewski
>             Fix For: 1.8.15.0
>
>         Attachments: asterisk.log, jira_asterisk_19985_v1.8.patch
>
>
> I've made a simple program which is calling to the firs user (test001), who is dialling local channel (I want him to be "on phone" all the time), after this originate made through AMI connects the new calls (in example made to user test002) with the local channel of test001 user via Bridge command. After the dialled user hangs up the first user (test001) goes to MOH.
> What I found out is that after some calls (sometimes 3, sometimes 30) after the hangup of dialled user, the test001 user does not go to MOH but on hangup.
> You can see in attached logs that usually after the bridge ends, there is a log stating:
> "features.c: starting new PBX in CC,park,3 for chan Local/12 at CC-be4b;2"
> but sometimes there is:
> "features.c: starting new PBX in CC,h,6 for chan Local/12 at CC-be4b;2"
> after this log the test001 user is disconnected.
> I've tried to pass this problem by. However it seems that the returning  context,priority,extension after the bridge is sometimes misplaced.
> I've attached the full logs.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira