Norman Posted February 7, 2009 Report Share Posted February 7, 2009 I am having an issue with Voice mail. Everything seems to work properly. The Log shows M messge next to calls with voice mail, but no voice mail ever saved or delivered. when I enable logging i see the following message [5] 2009/02/06 22:42:49: Message file recordings/msg42.wav was removed, removing associated message Please Help Thanks Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 7, 2009 Report Share Posted February 7, 2009 I am having an issue with Voice mail. Everything seems to work properly. The Log shows M messge next to calls with voice mail, but no voice mail ever saved or delivered.when I enable logging i see the following message [5] 2009/02/06 22:42:49: Message file recordings/msg42.wav was removed, removing associated message After leaving the message, does a new .msg file show up in the recordings directory? Maybe it is write protected? Quote Link to comment Share on other sites More sharing options...
Norman Posted February 7, 2009 Author Report Share Posted February 7, 2009 After leaving the message, does a new .msg file show up in the recordings directory? Maybe it is write protected? I am running the pbx process as root. I do not see anything in the recordings directory. Quote Link to comment Share on other sites More sharing options...
Friedom-Tech Posted February 8, 2009 Report Share Posted February 8, 2009 I am running the pbx process as root. I do not see anything in the recordings directory. do you have in the voicemail tab the option to delete the message? maybe it is sending via email and then deleting from the system? Quote Link to comment Share on other sites More sharing options...
lsantos Posted February 8, 2009 Report Share Posted February 8, 2009 I too am having the same issue. I've checked permissions on the "recordings" folder and everything is fine. I actually see the .msg files that the log reports as being deleted. I've checked the mailbox settings and I'm not confirgured to send messages via email. When you call into the mailbox, the system reports no new messages. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 9, 2009 Report Share Posted February 9, 2009 I too am having the same issue. I've checked permissions on the "recordings" folder and everything is fine. I actually see the .msg files that the log reports as being deleted. I've checked the mailbox settings and I'm not confirgured to send messages via email. When you call into the mailbox, the system reports no new messages. I still can't figure it out. It is hard to believe that would be a CentOS-specific problem. Last resort would be to make a strace of the interaction between the PBX and the kernel. Quote Link to comment Share on other sites More sharing options...
jag Posted February 9, 2009 Report Share Posted February 9, 2009 I still can't figure it out. It is hard to believe that would be a CentOS-specific problem. Last resort would be to make a strace of the interaction between the PBX and the kernel. If press # after ecording your message and then hangup, it works. If you just hangup, the pbx deletes the message. No email set. Tested snom, linksys, grandstream ata's. Tested on red hat. Does the same happen on windows? Quote Link to comment Share on other sites More sharing options...
Norman Posted February 9, 2009 Author Report Share Posted February 9, 2009 do you have in the voicemail tab the option to delete the message? maybe it is sending via email and then deleting from the system? No I do not have any voice mail tab. When I press pound in the end it does leave the message. otherwise it's not there. Quote Link to comment Share on other sites More sharing options...
lsantos Posted February 9, 2009 Report Share Posted February 9, 2009 I should have mentioned that I'm running on Red Hat as well with version 3.2.0.3143. I downgraded to 3.1.2.3120 and had the same exact problem. Took it down to 3.0.1.3023 and the problem went away. I should mention that I'm running 3.2.0.3143 on several CS410s and don't see this issue. Based on my experience and some of the other feedback on this topic, it appears this issue is affecting Red Hat and Windows releases 3.1.2 and higher. Quote Link to comment Share on other sites More sharing options...
pbx support Posted February 9, 2009 Report Share Posted February 9, 2009 I should have mentioned that I'm running on Red Hat as well with version 3.2.0.3143. I downgraded to 3.1.2.3120 and had the same exact problem. Took it down to 3.0.1.3023 and the problem went away. I should mention that I'm running 3.2.0.3143 on several CS410s and don't see this issue. Based on my experience and some of the other feedback on this topic, it appears this issue is affecting Red Hat and Windows releases 3.1.2 and higher. Hmm, did you check the extension settings to see whether the voice mail is disabled? (Just to see whether there's any issue with/during upgrade) Quote Link to comment Share on other sites More sharing options...
Norman Posted February 9, 2009 Author Report Share Posted February 9, 2009 Hmm, did you check the extension settings to see whether the voice mail is disabled? (Just to see whether there's any issue with/during upgrade) No everything is on. Like I mentioned on my previous post. When I hit # then 9 to accept the message is delivered. Otherwise it is not. Quote Link to comment Share on other sites More sharing options...
lsantos Posted February 9, 2009 Report Share Posted February 9, 2009 Yes, all my parameters are set correctly. As Norman mentioned, a #9 to accept the message works. Just hanging up causes the scenario described earlier. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 9, 2009 Report Share Posted February 9, 2009 Yes, all my parameters are set correctly. As Norman mentioned, a #9 to accept the message works. Just hanging up causes the scenario described earlier. May be a stupid question: Do you actually see the BYE message showing up on the PBX? Do you see it in the log file? Maybe the PBX is not aware the call disconnected yet. Quote Link to comment Share on other sites More sharing options...
lsantos Posted February 9, 2009 Report Share Posted February 9, 2009 Yes, there is a BYE message. I've attached the log file for your reference. pbxnsip.txt Quote Link to comment Share on other sites More sharing options...
lsantos Posted February 14, 2009 Report Share Posted February 14, 2009 Looking for an update on this issue. Quote Link to comment Share on other sites More sharing options...
pbx support Posted February 14, 2009 Report Share Posted February 14, 2009 Looking for an update on this issue. We are trying to reproduce it in our lab so that we can see where the problem is and fix it. So far the problem has not happened in our network. Is there anything special about the install directory/recordings directory? Quote Link to comment Share on other sites More sharing options...
lsantos Posted February 14, 2009 Report Share Posted February 14, 2009 The home path in this installation is "/home/PBXnSIP". Here are the permissions on the path directories: drwxrwxrwx 4 root root 4096 Nov 17 14:11 home drwxrwxrwx 36 root root 4096 Feb 14 00:00 PBXnSIP drwxr-xr-t 2 root root 4096 Feb 7 14:09 accesslist drwxr-xr-t 2 root root 4096 Feb 7 17:16 acds drwxr-xr-t 2 root root 4096 Feb 7 14:09 adrbook drwxr-xr-t 2 root root 4096 Feb 9 10:32 attendants drwxr-xr-t 2 root root 20480 Feb 7 14:26 audio_en drwxr-xr-t 2 root root 4096 Feb 7 14:20 audio_moh drwxr-xr-t 2 root root 4096 Feb 7 14:09 button_lists drwxr-xr-t 2 root root 4096 Feb 7 14:09 buttons drwxr-xr-t 2 root root 4096 Feb 7 17:16 callingcards drwxr-xr-t 2 root root 4096 Feb 8 14:40 calls drwxr-xr-t 2 root root 12288 Feb 14 10:56 cdr drwxr-xr-t 2 root root 4096 Feb 7 14:09 colines drwxr-xr-t 2 root root 4096 Feb 9 09:26 conferences drwxr-xr-t 2 root root 4096 Feb 9 14:39 dial_plan drwxr-xr-t 2 root root 4096 Feb 9 14:38 dial_plan_entry drwxr-xr-t 2 root root 4096 Feb 8 15:02 domain_alias drwxr-xr-t 2 root root 4096 Feb 8 15:02 domains drwxr-xr-t 2 root root 4096 Feb 9 10:31 extensions drwxr-xr-t 2 root root 4096 Feb 7 17:16 hoots drwxr-xr-t 2 root root 4096 Feb 7 17:16 hunts drwxr-xr-t 2 root root 4096 Feb 7 14:09 ivrnodes drwxr-xr-t 2 root root 4096 Feb 13 13:13 messages drwxr-xr-t 2 root root 4096 Feb 7 14:09 mohs lrwxrwxrwx 1 root root 24 Feb 9 17:19 pbxctrl -> pbxctrl-rhes4-3.2.0.3143 -rwxr-xr-x 1 root root 8172448 Nov 17 14:14 pbxctrl-rhes4-3.0.1.3023 -rwxr-xr-x 1 root root 7174304 Jan 28 13:29 pbxctrl-rhes4-3.1.2.3120 -rwxr-xr-x 1 root root 7340132 Jan 29 15:11 pbxctrl-rhes4-3.2.0.3143 drwxr-xr-t 2 root root 4096 Feb 7 14:09 pnp_parms drwxr-xr-t 2 root root 4096 Feb 13 13:13 recordings drwxr-xr-t 2 root root 4096 Feb 7 15:19 registrations drwxr-xr-t 2 root root 4096 Feb 7 14:09 schedules drwxr-xr-t 2 root root 4096 Feb 14 00:02 spool drwxr-xr-t 2 root root 4096 Feb 7 17:16 srvflags drwxr-xr-t 2 root root 4096 Feb 9 13:49 trunks drwxr-xr-t 2 root root 4096 Feb 9 11:34 user_alias drwxr-xr-t 2 root root 4096 Feb 9 10:32 users drwxr-xr-t 2 root root 4096 Feb 9 09:28 wipers Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 14, 2009 Report Share Posted February 14, 2009 Looking for an update on this issue. It looks like we have a race condition here. When a message is being recorded it takes some time (ms) until the file made it to the file system. If the check if the file is in the file system is quicker than the file system write, the PBX might really think that there files is not there and it will delete the message. Workaround: Hard to say. Probably we need to put in a extra safety belt that does not delete "young" messages. Quote Link to comment Share on other sites More sharing options...
lsantos Posted February 14, 2009 Report Share Posted February 14, 2009 Sounds like you've been able to replicate the problem. I'll await a fix. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 14, 2009 Report Share Posted February 14, 2009 Sounds like you've been able to replicate the problem. I'll await a fix. Can you try it out? We can make a test build for CentOS. Quote Link to comment Share on other sites More sharing options...
Carl Johnson Posted February 17, 2009 Report Share Posted February 17, 2009 We have had this EXACT same issue since some 3.1 versions .. please release the fix for Debian and SuSE as well .. Quote Link to comment Share on other sites More sharing options...
lsantos Posted February 17, 2009 Report Share Posted February 17, 2009 I have a RedHat environment. I'll be happy to try a test build for that environment. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 18, 2009 Report Share Posted February 18, 2009 I have a RedHat environment. I'll be happy to try a test build for that environment. Please try http://www.pbxnsip.com/protect/protect/pbx...hes4-3.3.0.3147. Quote Link to comment Share on other sites More sharing options...
lsantos Posted February 18, 2009 Report Share Posted February 18, 2009 This link does not work. Quote Link to comment Share on other sites More sharing options...
pbx support Posted February 18, 2009 Report Share Posted February 18, 2009 This link does not work. This should work http://www.pbxnsip.com/protect/pbxctrl-rhes4-3.3.0.3147 For Cent OS, please use http://www.pbxnsip.com/protect/pbxctrl-centos5-3.3.0.3147 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.