-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
action_redirect: remove after_bridge_goto_info #1160
base: master
Are you sure you want to change the base?
action_redirect: remove after_bridge_goto_info #1160
Conversation
Workflow PRCheck completed successfully |
cherry-pick-to: 20 |
18 no longer receives fixes. I have removed it from the cherry pick list. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a "Fixes:" or "Resolves:" trailer to both the PR description and the commit message or the related issue won't automatically close when this PR merges.
See:
https://docs.asterisk.org/Development/Policies-and-Procedures/Commit-Messages/
9d9703d
to
3c13dbc
Compare
Workflow PRCheck completed successfully |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You added the Resolves trailer to the commit message but not the PR description. It needs to be in the PR description as well or the related issue won't be automatically closed.
3c13dbc
to
d2cdda0
Compare
Workflow PRCheck failed |
d2cdda0
to
de729a3
Compare
Workflow PRCheck failed |
de729a3
to
2a77720
Compare
Under certain circumstances the context/extens/prio are stored in the after_bridge_goto_info. This info is used when the bridge is broken by for hangup of the other party. In the situation that the bridge is broken by an AMI Redirect this info is not used but also not removed. With the result that when the channel is put back in a bridge and the bridge is broken the execution continues at the wrong context/extens/prio. Resolves: asterisk#1144
2a77720
to
b13f3fa
Compare
Workflow PRCheck completed successfully |
Code modified. PS: This function is not intended for general use but a helper for action_redirect hence the _ |
Under certain circumstances the context/extens/prio are stored in the
after_bridge_goto_info. This info is used when the bridge is broken by
for hangup of the other party. In the situation that the bridge is
broken by an AMI Redirect this info is not used but also not removed.
With the result that when the channel is put back in a bridge and the
bridge is broken the execution continues at the wrong
context/extens/prio.
Resolves: #1144