[Home]

Summary:ASTERISK-28935: app_meetme tries to create audio files with format sln
Reporter:Pete Kirkham (pkirkham)Labels:
Date Opened:2020-06-04 12:18:32Date Closed:2020-06-20 12:00:01
Priority:MinorRegression?
Status:Closed/CompleteComponents:Applications/app_meetme
Versions:16.10.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:ubuntu 18.04 asterisk 16.10Attachments:
Description:line 3480:res = ast_play_and_record(chan, "vm-rec-name", user->namerecloc, 10, "sln", &duration, NULL, ast_dsp_get_threshold_from_settings(THRESHOLD_SILENCE), 0, NULL);

and

line 3482:res = ast_record_review(chan, "vm-rec-name", user->namerecloc, 10, "sln", &duration, NULL);
sln should be slin

however this didn(t solve my problem since I'd eliminated slin from the build.
It would appear that meetme considers slin is a prequisite
Comments:By: Asterisk Team (asteriskteam) 2020-06-04 12:18:32.959-0500

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.

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.
By: Joshua C. Colp (jcolp) 2020-06-04 12:28:32.066-0500

Those lines record into the signed linear file format, which is provided by the format_sln module using the "sln" file extension. This is correct, and is likely done because Meetme itself operates in signed linear so it is more efficient to save such files in signed linear.

What problem is actually occurring?
By: Pete Kirkham (pkirkham) 2020-06-06 04:41:30.814-0500

Hi Joshua,
OK I have misinterpreted the nature of the problem.
Here are the Log messages:

[Jun  4 16:12:49] VERBOSE[15403][C-00000001] app_meetme.c: Created MeetMe conference 1023 for conference '600'
[Jun  4 16:12:49] VERBOSE[15403][C-00000001] app.c: Recording
[Jun  4 16:12:49] VERBOSE[15403][C-00000001] file.c: <PJSIP/PortablePete-00000000> Playing 'vm-rec-name.slin' (language 'en_GB')
[Jun  4 16:12:54] VERBOSE[15403][C-00000001] file.c: <PJSIP/PortablePete-00000000> Playing 'beep.slin' (language 'en_GB')
[Jun  4 16:12:54] VERBOSE[15403][C-00000001] res_rtp_asterisk.c: 0x55f083dcca50 -- Strict RTP learning complete - Locking on source address 192.168.1.16:63270
[Jun  4 16:12:55] WARNING[15403][C-00000001] file.c: No such format 'sln'
[Jun  4 16:12:55] VERBOSE[15403][C-00000001] app.c: x=0, open writing:  /var/spool/asterisk/meetme/meetme-username-600-1 format: sln, (nil)
[Jun  4 16:12:55] WARNING[15403][C-00000001] app.c: Error creating writestream '/var/spool/asterisk/meetme/meetme-username-600-1', format 'sln'
[Jun  4 16:12:55] VERBOSE[15403][C-00000001] chan_dahdi.c: Hungup 'DAHDI/pseudo-890900189'
[Jun  4 16:12:55] VERBOSE[15403][C-00000001] pbx.c: Spawn extension (outgoing, 6000, 4) exited non-zero on 'PJSIP/PortablePete-00000000'
I'm not sure why DAHDI gets involved either since the origin of the call was a PJSIP softphone.

Best regards,
Pete

By: Joshua C. Colp (jcolp) 2020-06-06 07:58:03.154-0500

Is the format_sln module loaded? If not, then it should be for this functionality.

As well the legacy Meetme application uses DAHDI for its mixing and for conference recording/audio playback into it, thus why you see it.
By: Asterisk Team (asteriskteam) 2020-06-20 12:00:00.691-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines