[Home]

Summary:ASTERISK-30403: VoiceMailMain. Problem with pronouncing CallerID Number.
Reporter:Volodya Ivanets (Volodya)Labels:
Date Opened:2023-01-25 11:53:23.000-0600Date Closed:2023-01-25 12:49:01.000-0600
Priority:MinorRegression?
Status:Closed/CompleteComponents:Applications/app_voicemail
Versions:18.15.1 Frequency of
Occurrence		Constant
Related
Issues:
duplicatesASTERISK-30248 ast_get_digit_str adds bogus initial delimiter if first character not to be spoken
Environment:Attachments:
Description:If there is a "+" charachter in the CallerID Number section of the "callerid" line in VM message description file (for example /var/spool/asterisk/voicemail/default/106/Old/msg0000.txt), Asterisk will fail to playback phone number. Below is a fragment of an Asterisk CLI output. Unfortunately Jira removed extra spaces but in the CLI there are two spaces between {{File  does}} and {{open  (format}} which makes me assume that Asterisk attempts to playback a file with an empty name.

{quote}
   -- <SIP/106-00000554> Playing 'vm-from-phonenumber.gsm' (language 'en')
\[2023-01-25 12:12:33\] WARNING\[8926\]\[C-0000022c\]: file.c:824 ast_openstream_full: File  does not exist in any format
\[2023-01-25 12:12:33\] WARNING\[8926\]\[C-0000022c\]: file.c:1303 ast_streamfile: Unable to open  (format (alaw)): No such file or directory
 == Spawn extension (macro-check-voicemail, s, 14) exited non-zero on 'SIP/106-00000554' in macro 'check-voicemail'
{quote}
Comments:By: Asterisk Team (asteriskteam) 2023-01-25 11:53:25.852-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) 2023-01-25 11:59:29.894-0600

You've tagged this against Asterisk 18.16.0, is that correct? A fix already went in which includes that version that should have resolved this.
By: Volodya Ivanets (Volodya) 2023-01-25 12:45:56.158-0600

Sorry, it was by mistake. Asterisk version used is 18.15.1. Changed it.
Is it already fixed in 18.16.0? Thanks!
By: Joshua C. Colp (jcolp) 2023-01-25 12:47:01.879-0600

Yes, this has already been fixed.
By: Volodya Ivanets (Volodya) 2023-01-25 12:48:09.250-0600

Awesome, thank you!
By: Asterisk Team (asteriskteam) 2023-01-25 12:48:09.745-0600

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.