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

[Rusty Newton (JIRA)]

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

Rusty Newton edited comment on ASTERISK-20752 at 1/8/13 12:27 PM:
------------------------------------------------------------------

Can you verify that your patch follows the coding guidelines and perhaps have someone else test it out to confirm the fix?
                
      was (Author: rnewton):
    Can you verify that your patch follows the coding guidelines and perhaps someone else test it out to confirm?
                  
> 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, Channels/chan_sip/General
>    Affects Versions: 10.8.0
>            Reporter: Marcus Hunger
>            Assignee: 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