Skip to content

sig_analog: Add Call Waiting Deluxe support.#272

Merged
github-actions[bot] merged 1 commit into
asterisk:masterfrom
InterLinked1:master-issue-271
May 5, 2025
Merged

sig_analog: Add Call Waiting Deluxe support.#272
github-actions[bot] merged 1 commit into
asterisk:masterfrom
InterLinked1:master-issue-271

Conversation

@InterLinked1

Copy link
Copy Markdown
Contributor

Adds support for Call Waiting Deluxe options to enhance the current call waiting feature.

As part of this change, a mechanism is also added that allows a channel driver to queue an audio file for Dial() to play, which is necessary for the announcement function.

ASTERISK-30373 #close

Imported from Gerrit: https://gerrit.asterisk.org/c/asterisk/+/19748

Resolves: #271

@asterisk-org-access-app

Copy link
Copy Markdown

REMINDER: If this PR applies to other branches, please add a comment with the appropriate "cherry-pick-to" headers as per the Create a Pull Request process.

If you don't want it cherry-picked, please add a comment with cherry-pick-to: none so we don't keep asking.

If, after adding "cherry-pick-to" comments, you change your mind, please edit the comment to DELETE the header lines and add cherry-pick-to: none.

The currently active branches are now 18, 20, 21 and master.

@InterLinked1

InterLinked1 commented Aug 24, 2023

Copy link
Copy Markdown
Contributor Author

cherry-pick-to: 20
cherry-pick-to: 21
cherry-pick-to: 22

@InterLinked1

Copy link
Copy Markdown
Contributor Author

@asteriskteam Would someone mind giving this review in particular a look soon, if they have time? Don't want to nag, but because of the monolithic architecture of chan_dahdi, it's very difficult to do concurrent development for chan_dahdi so things have to be serialized. Thanks!

Comment thread include/asterisk/channel.h Outdated
@jcolp

jcolp commented Nov 2, 2023

Copy link
Copy Markdown
Member

@asteriskteam Would someone mind giving this review in particular a look soon, if they have time? Don't want to nag, but because of the monolithic architecture of chan_dahdi, it's very difficult to do concurrent development for chan_dahdi so things have to be serialized. Thanks!

The reality is that community members have no interest in reviewing these kind of changes, and personally I put such changes at the bottom of my todo list. You can continue to do development of chan_dahdi for your needs/interests/purposes, but the review times here are likely to continue to be a long time.

@asteriskteam

Copy link
Copy Markdown
Contributor

This PR has been marked stale because it has been in "Changes Requested" or "submitter-action-required" state for 28 days or more. Please make the requested changes within 14 days or the PR will be closed.

@asteriskteam

Copy link
Copy Markdown
Contributor

This PR has been closed because it has been in "Changes Requested" or "submitter-action-required" state for more than 42 days.

@InterLinked1

Copy link
Copy Markdown
Contributor Author

@jcolp Would you mind reopening this? Thanks!

@jcolp jcolp reopened this Oct 3, 2024
@jcolp

jcolp commented Oct 3, 2024

Copy link
Copy Markdown
Member

Request completed.

Comment thread include/asterisk/frame.h
Comment thread main/channel.c Outdated
Comment thread main/channel.c Outdated
Comment thread configs/samples/chan_dahdi.conf.sample
Comment thread channels/sig_analog.h Outdated
Comment thread channels/sig_analog.c
Comment thread channels/sig_analog.c
Comment thread channels/sig_analog.c
Comment thread channels/sig_analog.h Outdated
Comment thread funcs/func_frame_trace.c Outdated
@InterLinked1

Copy link
Copy Markdown
Contributor Author

@gtjoseph Is there any way to do a "recheck" on this? I'm not sure what this error is about but it's definitely irrelevant to the change. Thanks!

@gtjoseph

gtjoseph commented Oct 16, 2024

Copy link
Copy Markdown
Member

Is there any way to do a "recheck" on this? I'm not sure what this error is about but it's definitely irrelevant to the change. Thanks!

@InterLinked1 Well, I wouldn't say "definitely". :) The PR is based on a very old version of the "master" branch that doesn't have commit 64597bf which fixes the quoting of the 100rel column in contrib/ast-db-manage/config/versions/539f68bede2c_add_peer_supported_to_100rel.py. If you rebase the PR on current master and force-push, the alembic issue should go away.

@InterLinked1

Copy link
Copy Markdown
Contributor Author

Is there any way to do a "recheck" on this? I'm not sure what this error is about but it's definitely irrelevant to the change. Thanks!

@InterLinked1 Well, I wouldn't say "definitely". :) The PR is based on a very old version of the "master" branch

Yeah, if it hadn't been for the new commit after the GitHub migration, the commit would be from 2022 :)

that doesn't have commit 64597bf which fixes the quoting of the 100rel column in contrib/ast-db-manage/config/versions/539f68bede2c_add_peer_supported_to_100rel.py. If you rebase the PR on current master and force-push, the alembic issue should go away.

Okay, just gave that a try, hopefully that fixes it. Surprisingly, it rebased without any issues.

@asteriskteam

Copy link
Copy Markdown
Contributor

This PR has been marked stale because it has been in "Changes Requested" or "submitter-action-required" state for 28 days or more. Please make the requested changes within 14 days or the PR will be closed.

@InterLinked1

Copy link
Copy Markdown
Contributor Author

@jcolp Seems GitHub thinks changes are requested from your last input on this, would you mind giving this another review when you have a moment? Thanks!

@asteriskteam

Copy link
Copy Markdown
Contributor

This PR has been marked stale because it has been in "Changes Requested" or "submitter-action-required" state for 28 days or more. Please make the requested changes within 14 days or the PR will be closed.

@InterLinked1

Copy link
Copy Markdown
Contributor Author

This PR has been marked stale because it has been in "Changes Requested" or "submitter-action-required" state for 28 days or more. Please make the requested changes within 14 days or the PR will be closed.

@asteriskteam I have made the requested changes, could you please change the status of this? Thank you.

@InterLinked1

Copy link
Copy Markdown
Contributor Author

@jcolp Any chance you'll be able to take another look at this soon? Everything should be good to go now, but the UI still says it's pending a review from you.
Thanks!

@jcolp

jcolp commented Mar 28, 2025

Copy link
Copy Markdown
Member

Other reviews are higher on my list, so no idea.

@InterLinked1

Copy link
Copy Markdown
Contributor Author

Other reviews are higher on my list, so no idea.

I realize there's no SLA for reviews, but this patch is for a core supported module, and dates back to 2022, making it by far the oldest patch in the review queue. You also additionally asked for a community review - something seldom if ever required for other patches - which in any case was obtained half a year ago now. In light of that, I would at least hope its priority could be reconsidered.

@jcolp

jcolp commented Apr 2, 2025

Copy link
Copy Markdown
Member

I don't think I ever asked specifically for a community review? It was for someone else, it could have been someone Sangoma too. Reviews generally should have two reviews at a minimum.

@gtjoseph gtjoseph left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you rebase on current master and force-push? The manager checks are infinitely looping because your base branch doesn't have the updateconfig fixes you did a short time ago.

@github-actions

github-actions Bot commented Apr 3, 2025

Copy link
Copy Markdown

Attention! This pull request may contain issues that could prevent it from being accepted. Please review the checklist below and take the recommended action. If you believe any of these are not applicable, just add a comment and let us know.

  • The PR description does not match the commit message body. This can cause confusion for reviewers and future maintainers. GitHub doesn't automatically update the PR description when you update the commit message so if you've updated the commit with a force-push, please update the PR description to match the new commit message body.

Documentation:

@github-actions

github-actions Bot commented Apr 3, 2025

Copy link
Copy Markdown

Workflow PRCheck completed successfully

Adds support for Call Waiting Deluxe options to enhance
the current call waiting feature.

As part of this change, a mechanism is also added that
allows a channel driver to queue an audio file for Dial()
to play, which is necessary for the announcement function.

ASTERISK-30373 #close

Resolves: asterisk#271

UserNote: Call Waiting Deluxe can now be enabled for FXS channels
by enabling its corresponding option.
@InterLinked1

Copy link
Copy Markdown
Contributor Author

Attention! This pull request may contain issues that could prevent it from being accepted. Please review the checklist below and take the recommended action. If you believe any of these are not applicable, just add a comment and let us know.

  • The PR description does not match the commit message body. This can cause confusion for reviewers and future maintainers. GitHub doesn't automatically update the PR description when you update the commit message so if you've updated the commit with a force-push, please update the PR description to match the new commit message body.
  • A change was detected to the sample configuration files in ./config/samples but no UserNote or UpgradeNote was found in the commit message. If this PR includes changes that contain new configuration parameters or a change to existing parameters, please include a UserNote in the commit message. If the changes require some action from the user to preserve existing behavior, please include an UpgradeNote.

Documentation:

The "Imported from Gerrit" line is only in the PR description, I don't think that's needed/useful in the commit message.
I've added a UserNote.

@github-actions

github-actions Bot commented Apr 3, 2025

Copy link
Copy Markdown

Workflow PRCheck completed successfully

@asteriskteam

Copy link
Copy Markdown
Contributor

This PR has been marked stale because it has been in "Changes Requested" or "submitter-action-required" state for 28 days or more. Please make the requested changes within 14 days or the PR will be closed.

@github-actions

github-actions Bot commented May 5, 2025

Copy link
Copy Markdown

Workflow PRCPCheck completed successfully

@github-actions

github-actions Bot commented May 5, 2025

Copy link
Copy Markdown

Successfully merged to branch master and cherry-picked to ["20","21","22"]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[new-feature]: sig_analog: Add Call Waiting Deluxe support.

5 participants