[asterisk-bugs] [JIRA] (ASTERISK-20752) ringing/progress on branched calls not working correctly on some branched calls

[Marcus Hunger (JIRA)]

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

Marcus Hunger updated ASTERISK-20752:
-------------------------------------

    Description: 
There are certain call-scenarios where transmitting of ringing-information fails on asterisk.

1) a branched call, first leg replies 486 immediately, second leg replies with 183 first, 180 after it. caller hears silence since progress frames are dropped and no ringing-generator is activated.

2) similar to 1), branched call, first leg replies 486, second and third legs reply 183 and 180.

the calling leg is established already.

this behavior is shown at least by asterisk version 1.6 and 10.*. i was not able to test it with 11 yet.

A patch fixing this issue for me will be attached.

  was:
There are certain call-scenarios where transmitting of ringing-information fails on asterisk.

1) a branched call, first leg replies 486 immediately, second leg replies with 183 first, 180 after it. caller hears silence since progress frames are dropped and no ringing-generator is activated.

2) similar to 1), branched call, first leg replies 486, second and third legs reply 183 and 180.

this behavior is shown at least by asterisk version 1.6 and 10.*. i was not able to test it with 11 yet.

A patch fixing this issue for me will be attached.

    
> ringing/progress on branched calls not working correctly on some branched calls
> -------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20752
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20752
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_dial
>    Affects Versions: 10.8.0
>            Reporter: Marcus Hunger
>            Severity: Minor
>         Attachments: branchedprogress.patch
>
>
> There are certain call-scenarios where transmitting of ringing-information fails on asterisk.
> 1) a branched call, first leg replies 486 immediately, second leg replies with 183 first, 180 after it. caller hears silence since progress frames are dropped and no ringing-generator is activated.
> 2) similar to 1), branched call, first leg replies 486, second and third legs reply 183 and 180.
> the calling leg is established already.
> this behavior is shown at least by asterisk version 1.6 and 10.*. i was not able to test it with 11 yet.
> A patch fixing this issue for me will be attached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira