[asterisk-bugs] [JIRA] (ASTERISK-20752) ringing/progress on branched calls not working correctly on some branched calls
Richard Mudgett (JIRA)
noreply at issues.asterisk.org
Tue Dec 4 10:42:46 CST 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200395#comment-200395 ]
Richard Mudgett commented on ASTERISK-20752:
--------------------------------------------
You will also need to follow the coding guidelines:
https://wiki.asterisk.org/wiki/display/AST/Coding+Guidelines
> 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
More information about the asterisk-bugs
mailing list