[Home]

Summary:ASTERISK-29959: No timestamp on voicemail
Reporter:Schneur Rosenberg (thesipguy)Labels:
Date Opened:2022-03-08 05:50:33.000-0600Date Closed:
Priority:MinorRegression?
Status:Open/NewComponents:Applications/app_voicemail
Versions:18.10.1 Frequency of
Occurrence
Related
Issues:
Environment:Debian 9Attachments:( 0) vmdebug.txt
Description:Hi, I'm not sure if its a bug or a configuration issue, recently my customers were complaining that they cant hear the timestamp when listening to a voicemail, pressing 33 when retrieving voicemail only plays the caller ID, I have timezone set on the voicemail box.

Bellow is a sample voicemail config received from "voicemail show users for default"

=== Mailbox ...
===
=== ==> uniqueid: 17981
=== ==> context: default
=== ==> mailbox: XXXXXXXXXX
=== ==> password: XXXX
=== ==> tz: eastern
=== ==> attach: yes
=== ==> saycid: yes
=== ==> review: yes
=== ==> operator: yes
=== ==> envelope: yes
=== ==> sayduration: yes
=== ==> saydurationm: 0
=== ==> sendvoicemail: no
=== ==> delete: no
=== ==> nextaftercmd: yes
=== ==> forcename: no
=== ==> forcegreetings: no
=== ==> hidefromdir: yes
=== ==> tempgreetwarn: yes
=== ==> messagewrap: no
=== ==> minpassword: 4
=== ==> backupdeleted: 25
=== ==> maxsilence: 30

Bellow are the results from  "voicemail show zones"
Zone            Timezone             Message Format
european        Europe/Copenhagen    'vm-received' a d b 'digits/at' HM
military        Zulu                 'vm-received' q 'digits/at' H N 'hours' 'phonetic/z_p'
central24       America/Chicago      'vm-received' q 'digits/at' H N 'hours'
central         America/Chicago      'vm-received' Q 'digits/at' IMp
eastern         America/New_York     'vm-received' Q 'digits/at' IMp

Comments:By: Asterisk Team (asteriskteam) 2022-03-08 05:50:34.027-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].
By: Joshua C. Colp (jcolp) 2022-03-08 06:14:26.494-0600

We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information


By: Schneur Rosenberg (thesipguy) 2022-03-08 10:10:04.183-0600

Please find attached debug file
By: Sean Bright (seanbright) 2022-03-08 12:31:55.578-0600

The "new" say mode does not work for datetimes apparently. You can add the following to {{/etc/asterisk/say.conf}} to workaround it in the meantime:

{noformat}
[general]
mode = old
{noformat}
By: Schneur Rosenberg (thesipguy) 2022-03-09 03:22:29.993-0600

Sean, thanks this fixed my issue!, the ticket can be closed