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
Labels
Comments
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
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: