Skip to content
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

[bug]: func_channel: Some channel options are not settable #442

Closed
1 task done
InterLinked1 opened this issue Nov 11, 2023 · 0 comments · Fixed by #443
Closed
1 task done

[bug]: func_channel: Some channel options are not settable #442

InterLinked1 opened this issue Nov 11, 2023 · 0 comments · Fixed by #443
Assignees
Labels
bug support-level-core Functionality with core support level

Comments

@InterLinked1
Copy link
Contributor

Severity

Major

Versions

21.0.0

Components/Modules

func_channel

Operating Environment

N/A

Frequency of Occurrence

Constant

Issue Description

Some channel options are not settable, which prevents the user from being able to control them and means certain code is currently unreachable.

This adds support for setting and querying options that make sense to be exposed to users, which are not currently controllable in other ways. Documentation is also improved to describe how some of these options relate to other options.

Relevant log output

No response

Asterisk Issue Guidelines

  • Yes, I have read the Asterisk Issue Guidelines
InterLinked1 added a commit to InterLinked1/asterisk that referenced this issue Nov 11, 2023
Certain channel options are not set anywhere or
exposed in any way to users, making them unusable.
This exposes some of these options which make sense
for users to manipulate at runtime.

Resolves: asterisk#442
@jcolp jcolp added support-level-core Functionality with core support level and removed triage labels Nov 11, 2023
asterisk-org-access-app bot pushed a commit that referenced this issue Nov 28, 2023
Certain channel options are not set anywhere or
exposed in any way to users, making them unusable.
This exposes some of these options which make sense
for users to manipulate at runtime.

Resolves: #442
asterisk-org-access-app bot pushed a commit that referenced this issue Nov 28, 2023
Certain channel options are not set anywhere or
exposed in any way to users, making them unusable.
This exposes some of these options which make sense
for users to manipulate at runtime.

Resolves: #442
asterisk-org-access-app bot pushed a commit that referenced this issue Nov 28, 2023
Certain channel options are not set anywhere or
exposed in any way to users, making them unusable.
This exposes some of these options which make sense
for users to manipulate at runtime.

Resolves: #442
asterisk-org-access-app bot pushed a commit that referenced this issue Nov 28, 2023
Certain channel options are not set anywhere or
exposed in any way to users, making them unusable.
This exposes some of these options which make sense
for users to manipulate at runtime.

Resolves: #442
asterisk-org-access-app bot pushed a commit that referenced this issue Jan 12, 2024
Certain channel options are not set anywhere or
exposed in any way to users, making them unusable.
This exposes some of these options which make sense
for users to manipulate at runtime.

Resolves: #442
(cherry picked from commit 147f014)
asterisk-org-access-app bot pushed a commit that referenced this issue Jan 12, 2024
Certain channel options are not set anywhere or
exposed in any way to users, making them unusable.
This exposes some of these options which make sense
for users to manipulate at runtime.

Resolves: #442
(cherry picked from commit c222343)
asterisk-org-access-app bot pushed a commit that referenced this issue Jan 12, 2024
Certain channel options are not set anywhere or
exposed in any way to users, making them unusable.
This exposes some of these options which make sense
for users to manipulate at runtime.

Resolves: #442
(cherry picked from commit 9211fb5)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug support-level-core Functionality with core support level
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants