[asterisk-bugs] [JIRA] (ASTERISK-23690) Can't delete voicemail randomly

[Zacharie (JIRA)]

Zacharie created ASTERISK-23690:
-----------------------------------

             Summary: Can't delete voicemail randomly 
                 Key: ASTERISK-23690
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23690
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Applications/app_voicemail
    Affects Versions: 1.8.8.2
         Environment: Production
            Reporter: Zacharie


Some time when you try to delete voice messages from your phone by pressing 7 and 6 continuously, messages still show up after you disconnect and reconnect to voice mail.

This is what we can see in the log file :
Exact version is 1.8.3.3

Feb 5 17:34:46] DTMF[32304] channel.c: DTMF begin '7' received on SIP/75383-000024d5
[Feb 5 17:34:46] DTMF[32304] channel.c: DTMF begin ignored '7' on SIP/75383-000024d5
[Feb 5 17:34:46] DTMF[32304] channel.c: DTMF end '7' received on SIP/75383-000024d5, duration 190 ms
[Feb 5 17:34:46] DTMF[32304] channel.c: DTMF end passthrough '7' on SIP/75383-000024d5
[Feb 5 17:34:46] VERBOSE[32304] file.c: -- <SIP/75383-000024d5> Playing 'vm-deleted.gsm' (language 'fr')
[Feb 5 17:34:48] VERBOSE[32304] file.c: -- <SIP/75383-000024d5> Playing 'vm-last.gsm' (language 'fr')
[Feb 5 17:34:49] WARNING[32304] app_voicemail.c: No message attribute file?!! (/var/spool/asterisk/voicemail/GVMA_AGENTGROUP/56005/INBOX/msg0005.txt)
[Feb 5 17:34:49] VERBOSE[32304] file.c: -- <SIP/75383-000024d5> Playing 'vm-prev.gsm' (language 'fr')
[Feb 5 17:34:51] VERBOSE[32304] file.c: -- <SIP/75383-000024d5> Playing 'vm-advopts.gsm' (language 'fr')
[Feb 5 17:34:53] VERBOSE[32304] file.c: -- <SIP/75383-000024d5> Playing 'vm-repeat.gsm' (language 'fr')
[Feb 5 17:34:53] VERBOSE[32304] pbx.c: == Spawn extension (GVMA, 3856005, 3) exited non-zero on 'SIP/75383-000024d5'

It appears to be looking for msg0005 rather than msg0027 as present in folder so I presume this is where the problem lies.

Is there any known bug in my version?

Thanks in advance 



--
This message was sent by Atlassian JIRA
(v6.2#6252)