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

[new-feature]: callerid: Allow timezone to be specified at runtime #98

Closed
InterLinked1 opened this issue May 18, 2023 · 0 comments · Fixed by #99
Closed

[new-feature]: callerid: Allow timezone to be specified at runtime #98

InterLinked1 opened this issue May 18, 2023 · 0 comments · Fixed by #99
Assignees
Labels
new-feature support-level-core Functionality with core support level

Comments

@InterLinked1
Copy link
Contributor

Feature Description

The time zone used for Caller ID generation is currently hardcoded to the system time zone, and cannot be specified by modules using the Caller ID function. This makes it possible to optionally specify a tz format timezone.

InterLinked1 added a commit to InterLinked1/asterisk that referenced this issue May 18, 2023
The Caller ID generation routine currently is hardcoded
to always use the system time zone. This makes it possible
to optionally specify any TZ-format time zone.

Resolves: asterisk#98
ASTERISK-30330
@jcolp jcolp added support-level-core Functionality with core support level and removed triage labels May 18, 2023
gtjoseph pushed a commit that referenced this issue May 25, 2023
The Caller ID generation routine currently is hardcoded
to always use the system time zone. This makes it possible
to optionally specify any TZ-format time zone.

Resolves: #98
ASTERISK-30330
asteriskteam pushed a commit that referenced this issue May 25, 2023
The Caller ID generation routine currently is hardcoded
to always use the system time zone. This makes it possible
to optionally specify any TZ-format time zone.

Resolves: #98
ASTERISK-30330
asteriskteam pushed a commit that referenced this issue May 25, 2023
The Caller ID generation routine currently is hardcoded
to always use the system time zone. This makes it possible
to optionally specify any TZ-format time zone.

Resolves: #98
ASTERISK-30330
asterisk-org-access-app bot pushed a commit that referenced this issue Jun 30, 2023
The Caller ID generation routine currently is hardcoded
to always use the system time zone. This makes it possible
to optionally specify any TZ-format time zone.

Resolves: #98
ASTERISK-30330

(cherry picked from commit 8a03ed6)
asterisk-org-access-app bot pushed a commit that referenced this issue Jun 30, 2023
The Caller ID generation routine currently is hardcoded
to always use the system time zone. This makes it possible
to optionally specify any TZ-format time zone.

Resolves: #98
ASTERISK-30330

(cherry picked from commit 8a03ed6)
asterisk-org-access-app bot pushed a commit that referenced this issue Jun 30, 2023
The Caller ID generation routine currently is hardcoded
to always use the system time zone. This makes it possible
to optionally specify any TZ-format time zone.

Resolves: #98
ASTERISK-30330

(cherry picked from commit 8a03ed6)
asterisk-org-access-app bot pushed a commit that referenced this issue Jun 30, 2023
The Caller ID generation routine currently is hardcoded
to always use the system time zone. This makes it possible
to optionally specify any TZ-format time zone.

Resolves: #98
ASTERISK-30330

(cherry picked from commit 8a03ed6)
asterisk-org-access-app bot pushed a commit that referenced this issue Jun 30, 2023
The Caller ID generation routine currently is hardcoded
to always use the system time zone. This makes it possible
to optionally specify any TZ-format time zone.

Resolves: #98
ASTERISK-30330

(cherry picked from commit 8a03ed6)
asterisk-org-access-app bot pushed a commit that referenced this issue Jun 30, 2023
The Caller ID generation routine currently is hardcoded
to always use the system time zone. This makes it possible
to optionally specify any TZ-format time zone.

Resolves: #98
ASTERISK-30330

(cherry picked from commit d3227a6)
asterisk-org-access-app bot pushed a commit that referenced this issue Jul 10, 2023
The Caller ID generation routine currently is hardcoded
to always use the system time zone. This makes it possible
to optionally specify any TZ-format time zone.

Resolves: #98
ASTERISK-30330

(cherry picked from commit 8a03ed6)
asterisk-org-access-app bot pushed a commit that referenced this issue Jul 10, 2023
The Caller ID generation routine currently is hardcoded
to always use the system time zone. This makes it possible
to optionally specify any TZ-format time zone.

Resolves: #98
ASTERISK-30330

(cherry picked from commit d3227a6)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-feature support-level-core Functionality with core support level
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants