Saves voicemail, does not indicate on phone

Hi,

I just completed a v1.6 (dahdi) upgrade from v1.4 (zap), and now it will record a voicemail, but does not trigger the phone (polycom hardphone) to flash its voicemail indicator or send a message to my pager.

I believe this might have something to do with extensions.conf and the conversion. Where can I find a complete document on the syntax of this file?

I have the following:

[code][mainmenu-day]
exten => _1NXXNXXXXXX,1,Answer
exten => _1NXXNXXXXXX,2,Ringing
exten => _1NXXNXXXXXX,3,Wait(3)
exten => _1NXXNXXXXXX,4,Set(TIMEOUT(digit)=2)
exten => _1NXXNXXXXXX,5,Background(local-mainmenu-day)

exten => _1NXXNXXXXXX,6,Set(CALLERID(all)=0 - ${CALLERID(name)} <${CALLERID(num)}>)
exten => _1NXXNXXXXXX,7,Queue(operator,t,1)
exten => _1NXXNXXXXXX,8,Voicemail(7700@local,b)
exten => _1NXXNXXXXXX,9,Hangup
exten => _1NXXNXXXXXX,109,Hangup

exten => 2,1,Set(CALLERID(all)=2 - ${CALLERID(name)} <${CALLERID(num)}>)
exten => 2,2,Queue(sales,t,1)
exten => 2,3,Voicemail(7700@local,b)
exten => 2,4,Hangup
exten => 2,104,Hangup[/code]

When the call comes in, it looks like this (myname and myphone and my extension have been changed)

-- Starting simple switch on 'DAHDI/1-1' -- Executing [s@incoming:1] NoOp("DAHDI/1-1", "CALLERID = MYPHONE - 9735551212") in new stack -- Executing [s@incoming:2] Goto("DAHDI/1-1", "incoming,_1NXXNXXXXXX,1") in new stack -- Goto (incoming,_1NXXNXXXXXX,1) -- Executing [_1NXXNXXXXXX@incoming:1] Answer("DAHDI/1-1", "") in new stack -- Executing [_1NXXNXXXXXX@incoming:2] Ringing("DAHDI/1-1", "") in new stack -- Executing [_1NXXNXXXXXX@incoming:3] Wait("DAHDI/1-1", "3") in new stack -- Executing [_1NXXNXXXXXX@incoming:4] Set("DAHDI/1-1", "TIMEOUT(digit)=2") in new stack -- Digit timeout set to 2.000 -- Executing [_1NXXNXXXXXX@incoming:5] BackGround("DAHDI/1-1", "local-mainmenu-day") in new stack -- <DAHDI/1-1> Playing 'local-mainmenu-day.slin' (language 'en') -- Executing [2@incoming:1] Set("DAHDI/1-1", "CALLERID(all)=2 - MYPHONE <9735551212>") in new stack -- Executing [2@incoming:2] Queue("DAHDI/1-1", "sales,t,,,1") in new stack -- Started music on hold, class 'default', on DAHDI/1-1 -- Stopped music on hold on DAHDI/1-1 -- Executing [2@incoming:3] VoiceMail("DAHDI/1-1", "7700@local,b") in new stack -- <DAHDI/1-1> Playing 'vm-theperson.gsm' (language 'en') -- <DAHDI/1-1> Playing 'digits/7.gsm' (language 'en') -- <DAHDI/1-1> Playing 'digits/7.gsm' (language 'en') -- <DAHDI/1-1> Playing 'digits/0.gsm' (language 'en') -- <DAHDI/1-1> Playing 'digits/0.gsm' (language 'en') -- <DAHDI/1-1> Playing 'vm-isonphone.gsm' (language 'en') -- <DAHDI/1-1> Playing 'vm-intro.gsm' (language 'en') -- <DAHDI/1-1> Playing 'beep.gsm' (language 'en') -- Recording the message -- x=0, open writing: /var/spool/asterisk/voicemail/local/7700/tmp/KmSxkZ format: wav, 0x7f605c005ec8 -- Recording automatically stopped after a silence of 10 seconds -- <DAHDI/1-1> Playing 'auth-thankyou.gsm' (language 'en') == Parsing '/var/spool/asterisk/voicemail/local/7700/INBOX/msg0005.txt': == Found == Parsing '/var/spool/asterisk/voicemail/local/7700/INBOX/msg0005.txt': == Found -- Executing [2@incoming:4] Hangup("DAHDI/1-1", "") in new stack == Spawn extension (incoming, 2, 4) exited non-zero on 'DAHDI/1-1' -- Executing [h@incoming:1] Hangup("DAHDI/1-1", "") in new stack == Spawn extension (incoming, h, 1) exited non-zero on 'DAHDI/1-1' -- Hungup 'DAHDI/1-1'

If I manually dial into voicemail the message is there, but it’s not completing that final step where it alerts me that a voicemail has been received.

Any ideas greatly appreciated.
Thanks,
Alex

Hi,

Does anyone have any ideas about this problem? I’m really stuck, and this is our production voicemail server.

What would be the reason why it wouldn’t trigger the phone to alert the user of a new voicemail?

What further information can I provide to troubleshoot this problem?

Thanks,
Alex

[quote]What further information can I provide to troubleshoot this problem?
[/quote]

SIP debug for one and the sip.conf for the set in question.

Hi, thanks for your help.

I’ve enabled sip debug, and it prints a few blocks of messages like these:

<--- SIP read from UDP:192.168.1.23:5060 ---> SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK1b0b8076;rport From: "asterisk" <sip:asterisk@192.168.1.2>;tag=as54b326be To: <sip:7000@192.168.1.23>;tag=C22C13B6-99416FD7 CSeq: 102 OPTIONS Call-ID: 3450f2c54d83c6814f0179f24f21b2f5@192.168.1.2 Contact: <sip:7000@192.168.1.23> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER User-Agent: PolycomSoundPointIP-SPIP_500-UA/1.6.2.0041 Content-Length: 0

Is there something more specific I can do to provide info on what it’s doing as it’s leaving the voicemail?

I can dial out successfully using this phone, and I can also check the voicemails that have been received, despite there not being any flashing light indicating a voicemail exists.

My sip.conf is quite simple:

[general]
port            = 5060
bindaddr        = 192.168.1.2
context         = incoming
limitonpeers    = yes

deny            = 0.0.0.0/0.0.0.0
permit          = 192.168.1.0/255.255.255.0

[7000]
type            = friend
accountcode     = admin
host            = dynamic
username        = Admin
secret          = Admin-7000
mailbox         = 7000@local,7000@local
dtmfmode        = rfc2833
callerid        = General Voicemail Box <7000>
context         = trusted
qualify         = yes
canreinvite     = no
call-limit      = 5

Thanks again,
Alex

just an observation.

You posted the sip info for account 7000. In the cli output the voicemail message was left to mailbox 7700.

And you didn’t post any relevant SIP dialogue; I don’t think OPTIONs are relevant to MWI settings.

You need any INVITE, PUBLISH and SUBSCRIBE messages for the relevant device, with the corresponding immediate and delayed responses.

Sorry about that. The 7000 sip info is the same. Cut-and-paste error.

Thanks again,
Alex

Hi You have defined

mailbox 7000@local

is the voicemail.conf set with a context local in it.

also why twice ?
mailbox = 7000@local,7000@local

[quote=“ianplain”]Hi You have defined

mailbox 7000@local

is the voicemail.conf set with a context local in it.[/quote]
Is that a question? Can you point me to documentation to where the options in that file are defined?

[quote]also why twice ?
mailbox = 7000@local,7000@local[/quote]
It looks like this was indeed the problem. Not sure how that got there. Perhaps at one time it was for two extensions, like 7000@local,7007@local?

I removed the duplicate and it now seems to work.

Thanks,
Alex

check out /etc/asterisk/vm_general.inc
is there a simicolon at
;pollmailboxes=yes —

If so remove it and try again.

isnt the purpose of pollmailboxes=yes for when you add messages to the voicemail store from sources than the asterisk server? This causes asterisk to poll the mailboxes and if it notices any new vm’s then alert the phone.

I just know when I removed the semicolon, the voicemail light on my phones started working. You do want asterisk to poll the phones but with the semicolon there, it won’t.

[quote=“asterisk21st”]I just know when I removed the semicolon, the voicemail light on my phones started working. You do want asterisk to poll the phones but with the semicolon there, it won’t.

It looks like pollmailboxes=yes is the default:

;pollmailboxes=no ; If mailboxes are changed anywhere outside of app_voicemail, ; ; then this option must be enabled for MWI to work. This ; ; enables polling mailboxes for changes. Normally, it will ; ; expect that changes are only made when someone called in ; ; to one of the voicemail applications. ; ; Examples of situations that would require this option are ; ; web interfaces to voicemail or an email client in the case ; ; of using IMAP storage. ; ;pollfreq=30 ; If the "pollmailboxes" option is enabled, this option ; ; sets the polling frequency. The default is once every ; ; 30 seconds.

mine reads

pollmailboxes=yes ;pollfreq=30

I just wanted to let any users of the Asterisk GUI know that when the GUI writes the extension information to the users.conf (that’s where the GUI puts all of the user extension stuff) that it is not writing @default after mailbox=XXX for each user. I just upgraded two of my production servers to 1.6 which both had functional MWI under 1.4 and I had to go through and add @default to the end of each of my users mailbox lines. Then I reloaded asterisk and voila, in an instant the MWI lights began working as they should!! Now if I can get the BLF working on the Aastra 6757’s on one of my systems which worked under 1.4 I’ll be golden.