2.3.0beta2.2 module updates as of now
When creating a new extension the default folder structure is not getting made in
I only have 2 folders there right now, but there are 10 extensions.
do ‘ls -la’ and post output?
[code:1]/var/spool/asterisk]# ls -la
drwxrwx— 8 asterisk asterisk 4096 Jul 22 13:21 .
drwxr-xr-x 14 root root 4096 Jul 22 11:42 …
drwxrw-rw- 2 asterisk asterisk 4096 Jul 22 11:42 fax
drwxrwx— 2 asterisk asterisk 4096 Apr 25 12:57 meetme
drwxrwxr-x 2 asterisk asterisk 4096 Apr 25 12:57 monitor
drwx-w---- 2 asterisk asterisk 4096 Jul 22 11:42 outgoing
drwxrwxr-x 2 asterisk asterisk 4096 Jul 22 13:21 tmp
drwxrwx— 4 asterisk asterisk 4096 Jul 22 11:42 voicemail[/code:1]
[code:1]/var/spool/asterisk/voicemail]# ls -la
drwxrwx— 4 asterisk asterisk 4096 Jul 22 11:42 .
drwxrwx— 8 asterisk asterisk 4096 Jul 22 13:21 …
drwxrwx— 4 asterisk asterisk 4096 Jul 22 16:02 default
drwxrwxr-x 2 asterisk asterisk 4096 Jul 24 10:44 device[/code:1]
[code:1]/var/spool/asterisk/voicemail/default]# ls -la
drwxrwx— 4 asterisk asterisk 4096 Jul 22 16:02 .
drwxrwx— 4 asterisk asterisk 4096 Jul 22 11:42 …
drwxrwx— 3 asterisk asterisk 4096 Jul 22 11:42 1234
drwx-w---- 8 asterisk asterisk 4096 Jul 22 17:02 500[/code:1]
Those last 2 dirs were made when I was running under beta1, ext 500 has since been deleted - but the dir remains.
what happens if you create the dir structure for an extension by hand? does it work?
nothing changed there. Are you running in extensions mode or deviceanduser mode? When you run in the latter mode, it is not always obvious - if the device is not fixed, the link doesn’t happen until a user logs onto it.
AMPEXTENSIONS=extensions - so nothing tricky there.
[code:1][[email protected] 599]# ls -l
drwx-w---- 8 asterisk asterisk 4096 Jul 24 20:57 500
-rw-rw---- 1 asterisk asterisk 8481 Jul 24 21:47 busy.gsm
drwx-w---- 2 asterisk asterisk 4096 Jul 24 20:57 greet
drwx-w---- 2 asterisk asterisk 4096 Jul 24 20:57 INBOX
drwx-w---- 2 asterisk asterisk 4096 Jul 24 20:57 Old
drwx-w---- 2 asterisk asterisk 4096 Jul 24 20:57 temp
drwx-w---- 2 asterisk asterisk 4096 Jul 24 20:57 tmp
drwx-w---- 2 asterisk asterisk 4096 Jul 24 20:57 unavail
-rw-rw---- 1 asterisk asterisk 8481 Jul 24 21:47 unavail.gsm[/code:1]
hmm - so you create a new extension and the link is not created for you? This part of the code has not been touched for quite some time so I can’t think of anything that may have changed it? Anyone else running across something like this in extensions mode?
ya - doesnt create folder - also forgot to explain the listing above - I copied the folder structure into a new folder for ext 599 - which had none before, and made the busy and unavailable messages, but I still get an error when calling the extension vmail.
Here is the output from a test call after copying the files listed in my previous post into a folder for the ext
One note - this system is running auth=database - and I did assign a department to the administrator that created this user, then later deleted the department, but it still doesnt make the mailbox - dont know if that has any tie - as far as creating a context for the department and any users created by that admin.???
I found that if I had “Smallest Download” (.gsm) checked in the ARI settings-Audio Format, files were not being created. I changed the format to .wav and normality returned. This looks like a per extension setting.
I am not real sure if that is helpful. Be curious to know?
slightly different problem - it doesnt even create the folder for the extension when I make a new user.
ie - As soon as I create new extension 510 and Apply changes, I should see a folder pop up in /var/spool/asterisk/voicemail/default/ that says 510 - but I get nothing.
OK - I think this is working fine and from memory I think my observations is now the code work:
I created an extension, nothing in defaults. I then called into that extension’s voicemail and crated a greeting. The folder, with the greeting is now there.
Second scenario - I created an extension, no folder. I then made a call to that extensions and let it drop into voicemail. Afterwards, folder and message left.
The link does not get created until first used one way or another. On these tests (beta2) these worked fine. You may want to go back to an older system, I suspect you will see the same results (since we really have not touched this part of the code).
I figured that, so I try to call in to leave a vmail and get an announcement “An error has occured, good bye”
See the attachment in the trac for how that goes
I am now on asterisk 1.2.22, and will try re installing 2.3 from source again to see if that fixes it.
[quote=“totalimpact”]I figured that, so I try to call in to leave a vmail and get an announcement: “An error has occured, good bye”
See the attachment in the trac for how that goes:
I am now on asterisk 1.2.22, and will try re installing 2.3 from source again to see if that fixes it.[/quote]
I see that it is failing getting to voicemail, don’t know what the issue is. I can say when I tried the two tests, creating extension and then calling to it before and after creating a greeting - it worked???
i figured it out - it was tied to the administrator module like i thought - after assigning a department to an admin, and then deleting the department it was linking all users created to a blank vmail context, no matter which admin made the user.
Even specifying the default context when creating a new user did not put them in that context, they were still under the blank context.
I made a new admin to see if that would fix it, but all admins on the system were somehow linked to a blank context - the result of this was apparent in /etc/asterisk/voicemail.conf:
 <<<<<<<this is the problem*********
500 => 5564,test,attach=no|saycid=no|envelope=no|delete=no
586 => 23426,test,attach=no|saycid=no|envelope=no|delete=no
587 => 234236,test5,attach=no|saycid=no|envelope=no|delete=no
598 => 23427,test4,attach=no|saycid=no|envelope=no|delete=no
after removing the blank  context everything worked.