|Summary:||ASTERISK-17000: File dir-welcome does not exist in any format|
|Reporter:||Andrew Thomas (raffles)||Labels:|
|Date Opened:||2010-11-22 07:10:11.000-0600||Date Closed:||2011-06-07 14:10:10|
|Environment:||Attachments:||( 0) issue0018351.txt|
|Description:||Is it me - or have you changed the file name that the directory application now looks for?|
It 'used' to look for 'dir-intro' - it now looks for 'dir-welcome' - which, if not found, stops the directory application working.
I fixed it by copying dir-intro to dir-welcome - but that's a work-around - not a fix ;).
|Comments:||By: Paul Belanger (pabelanger) 2010-11-24 19:58:25.000-0600|
We require a complete debug log to help triage the issue.
This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue:
By: Andrew Thomas (raffles) 2010-11-25 08:30:42.000-0600
Seriously? Surely a simple CLI output will suffice for such a small problem?
== Parsing '/etc/asterisk/voicemail.conf': == Found
== Parsing '/etc/asterisk/users.conf': == Found
-- <SIP/801-00000002> Playing 'dir-welcome.gsm' (language 'en')
== Spawn extension (dv-ip, *118, 1) exited non-zero on 'SIP/801-00000002'
exten => *118,1,Directory(dv-ip)
As you can see, it plays 'dir-welcome' not 'dir-intro' any more.
Let me know EXACTLY what you require as far as verbose and debugging goes and I'll accommodate as required.
By: Paul Belanger (pabelanger) 2010-11-25 11:40:49.000-0600
I did exactly tell you what we need, did you read the wiki page titled 'Collecting Debug Information'? Additionally, which Asterisk core sounds version do you have installed?
You should have the latest: http://downloads.asterisk.org/pub/telephony/sounds/asterisk-core-sounds-en-gsm-current.tar.gz
By: Andrew Thomas (raffles) 2010-11-26 03:12:03.000-0600
There you go. We have custom sound files that worked a treat until this little 'change'.
BTW - when did this change occur? Oh, and why?
By: David Woolley (davidw) 2010-11-26 05:12:36.000-0600
The way to find out when and why, in most cases, is to use svn blame to find out the revision in which the line was changed and then use svn log, with that revision number, to get the revision comments.
If the line has been changed multiple times, you can re-run svn blame with a -r parameter one less than the most recent change.
By: Leif Madsen (lmadsen) 2010-12-07 10:19:30.000-0600
From what I found this was changed a LONG time ago.... unless I've looked this up incorrectly:
lmadsen@scooter:~/src/1.8$ svn log -r 110237
r110237 | tilghman | 2008-03-20 01:06:12 -0400 (Thu, 20 Mar 2008) | 5 lines
Upgrade the sounds version; add several directory enhancements:
1) Number of digits to enter can now be configured
2) The digits can now match on both first AND last name, instead of only one or the other
(Closes issue ASTERISK-6965)
By: Andrew Thomas (raffles) 2010-12-08 04:59:32.000-0600
Errr - I don't see mention of a file name change in there (maybe I didn't look hard enough).
220.127.116.11 uses dir-intro
1.4.35 uses dir-intro
1.4.36 uses dir-intro
18.104.22.168 crashes out (stops Asterisk) - I've never noticed that before. Needs a separate issue reporting by me.
22.214.171.124 uses dir-welcome
By: David Woolley (davidw) 2010-12-08 05:01:21.000-0600
126.96.36.199 isn't supported, so there is no point in reporting an issue that only applies to it.
By: Andrew Thomas (raffles) 2010-12-08 05:12:10.000-0600
I'll upgrade that system ASAP then :)
By: Andrew Thomas (raffles) 2011-01-18 10:52:54.000-0600
Why has this been closed? The 'problem' still exists.
Anyone using 'older' Asterisk versions now have their 'directory' application broken. All due to this file name change.
The linked report has nothing to do with this - as that goes way back to 2008 - and the name change came only as recent as 2010 (may have been 2009 for 'testing' versions)!
EDIT : By 'older' Asterisk - I mean that if they are using old sounds (custom ones for example) and upgrade just Asterisk to a later version. Sorry for the confusion...
By: Sean Bright (seanbright) 2011-01-19 10:11:59.000-0600
OK. A few things...
This was indeed changed in r110237 back in 2008 but didn't make it into a release that you were using until 2010.
You can still use the directoryintro option in voicemail.conf (either in the [general] section or a specific voicemail context like:
Which will restore the previous functionality. Note that the 'directoryintro' configuration variable was available before r110237 as well.
Finally, installing the updated core sounds package resolves this issue, as it installs the necessary dir-welcome sound file.
What, specifically, would you like us to do so that you can consider this issue closed?
By: Leif Madsen (lmadsen) 2011-01-19 14:46:54.000-0600
This is not an issue. Closing.