Issue with some voicemail boxes

I have inherited the administration of a FreePBX system. Never worked with one before and unfamiliar with Linux.

We are having an issue with a couple of mailboxes, one of which is mine. The phone extensions show that there are voicemails, but when you try to access the mailbox via phone it says “login incorrect”. When attempting to leave those extensions a voicemail the system says “I’m sorry” and disconnects. I have the password set in Applications/Extensions tab and also in Settings/Voicemail Admin set to the same. I can login to the user panel for those extensions using ext # and voicemail password.

What I can tell its version 2.11.0.43.

When I try to paste in the text from Asterisk Logfile 500 full to show what happens when attempting to get voicemail from my extension it says new users cannot paste links

500

Show
[2019-07-02 06:42:04] VERBOSE[20965][C-0047496e] file.c: – <SIP/261-0004508c> Playing ‘vm-password.ulaw’ (language ‘en’)
[2019-07-02 06:42:08] VERBOSE[20965][C-0047496e] app_voicemail.c: – Incorrect password ‘1234’ for user ‘261’ (context = default)
[2019-07-02 06:42:08] VERBOSE[20965][C-0047496e] file.c: – <SIP/261-0004508c> Playing ‘vm-incorrect-mailbox.ulaw’ (language ‘en’)
[2019-07-02 06:42:10] VERBOSE[20965][C-0047496e] pbx.c: – Executing [[email protected]:1] Hangup(“SIP/261-0004508c”, “”) in new stack
[2019-07-02 06:42:10] VERBOSE[20965][C-0047496e] pbx.c: == Spawn extension (from-internal, h, 1) exited non-zero on ‘SIP/261-0004508c’
[2019-07-02 06:42:10] VERBOSE[20965][C-0047496e] cdr_adaptive_odbc.c: > [INSERT INTO cdr (calldate,clid,src,dst,dcontext,channel,lastapp,duration,billsec,disposition,amaflags,uniqueid,cnum,cnam) VALUES ({ ts ‘2019-07-02 06:41:57’ },’“Scott Baalman” <261>’,‘261’,’*97’,‘from-internal’,‘SIP/261-0004508c’,‘VoiceMailMain’,13,13,‘ANSWERED’,3,‘1562074917.2511830’,‘261’,‘Scott Baalman’)]
[2019-07-02 06:42:10] VERBOSE[2046] cel_odbc.c: > [INSERT INTO cel (eventtype,eventtime,cid_name,cid_num,cid_ani,cid_rdnis,cid_dnid,exten,context,channame,appname,appdata,amaflags,accountcode,uniqueid,linkedid,peer,userdeftype,userfield) VALUES (‘HANGUP’,{ts ‘2019-07-02 06:42:10’},‘Scott Baalman’,‘261’,‘261’,’’,’*97’,‘h’,‘from-internal’,‘SIP/261-0004508c’,’’,’’,3,’’,‘1562074917.2511830’,‘1562074917.2511830’,’’,’’,’’)]
[2019-07-02 06:42:10] VERBOSE[2046] cel_odbc.c: > [INSERT INTO cel (eventtype,eventtime,cid_name,cid_num,cid_ani,cid_rdnis,cid_dnid,exten,context,channame,appname,appdata,amaflags,accountcode,uniqueid,linkedid,peer,userdeftype,userfield) VALUES (‘CHAN_END’,{ts ‘2019-07-02 06:42:10’},‘Scott Baalman’,‘261’,‘261’,’’,’*97’,‘h’,‘from-internal’,‘SIP/261-0004508c’,’’,’’,3,’’,‘1562074917.2511830’,‘1562074917.2511830’,’’,’’,’’)]
[2019-07-02 06:42:10] VERBOSE[2046] cel_odbc.c: > [INSERT INTO cel (eventtype,eventtime,cid_name,cid_num,cid_ani,cid_rdnis,cid_dnid,exten,context,channame,appname,appdata,amaflags,accountcode,uniqueid,linkedid,peer,userdeftype,userfield) VALUES (‘LINKEDID_END’,{ts ‘2019-07-02 06:42:10’},‘Scott Baalman’,‘261’,‘261’,’’,’*97’,‘h’,‘from-internal’,‘SIP/261-0004508c’,’’,’’,3,’’,‘1562074917.2511830’,‘1562074917.2511830’,’’,’’,’’)]
[2019-07-02 06:42:37] NOTICE[2063] chan_sip.c: Registration from ‘sip:[email protected]’ failed for ‘37.46.121.230:2501’ - Wrong password
[2019-07-02 06:42:41] NOTICE[2063] chan_sip.c: Registration from ‘sip:[email protected]’ failed for ‘178.33.117.246:33290’ - Wrong password

Look for a strange line in/etc/asterisk/voicemail.conf that has an opening [ but no closing ] if you find one, delete it.

There are a couple of approaches.

First, log in to the server as root and run “fwconsole chown” just to make sure the permissions on the VM folders are correct.

Next, log into the GUI and go to your extension. Under the VM tab, change the password on your mail box to the extension number. Try to access your VM - it should ask you for a new vmail passcode.

You may also be able to access the VM settings from User Manager.

There’s also a generalized voicemail module that allows you to do a lot of “overarching” VM stuff.

One of those should get you going.

These are phones failing to register with their SIP passwords (these are Chan-SIP extensions) so you need to fix that. The SIP password and the VM password are different, and the phone needs to have the SIP password to register.

No, those are attempted attacks. OP does not have extensions in those ranges, nor AFAIK any in France or Sweden.

Good catch.

How do I find the voicemail.conf in order to look at it? Sorry, little to no Linux experience

In the directory /etc/asterisk as stated :-).

https://www.tldp.org/LDP/Bash-Beginners-Guide/html/Bash-Beginners-Guide.html

If you are a m$ person use winscp

Here’s what I found towards the end of the voicemail.conf file. Since I’m a n00b at this, I assume this is wrong as the extensions we are having issues with are after the []

Should I move them before the [] ?

No, as I suggested at the beginning, delete the malformed line

Sorry, forgot to paste, here are the last few lines of the file. The extensions that are causing issues are the last 3 lines

200 => 1234,Operator,attach=no|saycid=no|envelope=yes|delete=no
280 => 1234,Gary Holland,attach=yes|saycid=no|envelope=no|delete=no
201 => 1234,Doug Cobillas,attach=yes|saycid=no|envelope=no|delete=no
254 => 1234,Marc Freedman,attach=yes|saycid=no|envelope=no|delete=no
[]
308 => 1234,Michael Littlefield,attach=yes|saycid=no|envelope=no|delete=no
227 => 1234,Michael Littlefield,attach=no|saycid=yes|envelope=yes|delete=no
261 => 12345,Scott Baalman,attach=no|saycid=yes|envelope=yes|delete=no

Or just delete the [] ?

Just delete that line which effectively puts 308,227 and 261 in a ‘null’ voicemail context.

So just delete out the line with [] and copy the file back to the system. Really that easy?

Won’t need to reboot system or anything? Sorry for all the questions

Be careful if you are a windoze or Mac person, line terminations vary by OS and editor used , easiest and safest from bash

sed -i 's/\[\]//' /etc/asterisk/voicemail.conf

No need to reboot but

rasterisk -x 'voicemail reload'

Is advised

Thanks! That solved the issue! I owe you a beer

2 Likes

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.