Jump to content

Cannot leave VM


Norman
 Share

Recommended Posts

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

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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)

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...