On 4/27/06, Bjorn Asmul <[EMAIL PROTECTED]> wrote:
You could also fiddle with the settings in voicemail.conf, such as: maxsilence silencethreshold minmessage http://www.voip-info.org/wiki-Asterisk+config+voicemail.conf -- Bjorn
Hi Bjorn, I've posted the same message to the asterisk-users mailing list and had pretty much the same responses.. Here is a copy of my message regarding maxsilence and minmessage settings: "ideally there should be a setting to simply remove a voicemail message that contains nothing but silence, but that's not what the maxsilence setting is for. Once you start recording a voicemail message, if you stop talking, a timer begins counting. If you don't speak for maxsilence seconds, you get disconnected. It is, however, possible to use maxsilence in conjunction with the minmessage setting to prevent empty voicemails from being left, by simply setting minmessage to be 1 second longer than the maxsilence setting. So if someone hangs up before leaving a voicemail message, but the system doesn't disconnect them immediately, the system stops the recording after maxsilence (ie 3 seconds), but if you have minmessage set to 4, asterisk will abandon the message. The problem is, if someone calls and then maybe gets sidetracked, or has to speak to someone else for a few seconds, or pick up their cell phone, in the middle of leaving a message, they'll get disconnected. So this still isn't a solution. The only thing I can think of is to run a script (specified by externnotify) after a voicemail message is left, which runs some type of audio analysis process to determine whether the sound file actually contains anything, and if not, delete it. I'm not sure what tool I can use to do the silence detection (I checked the manpage for sox, but it seems to only be able to remove silence from the beginning/end of a file, not report whether a file has silence or not)." I've since been contacted by Doug Vilim from Sangoma, and he says they've been able to reproduce the problem in-house and are working on a solution. Apparently it also occurs with cards from other vendors, so they believe it's a configuration issue (not sure if it's a zaptel config issue, or an asterisk one). Anyways, I'll keep everyone posted of any updates that I get. Mike
-----Original Message----- From: Mike Garey [mailto:[EMAIL PROTECTED] Sent: Monday, April 24, 2006 2:21 PM To: [email protected] Subject: [on-asterisk] Does Bell provide Remote Disconnect Supervision? We're having some problems on our asterisk box where a user calls in through a PSTN line, gets to voicemail, but hangs up before leaving a message, yet asterisk doesn't realize the phone has been disconnected and starts recording an empty message, which of course can become very annoying. I also notice that when calling from a PSTN line and ringing an extension, then immediately hanging up, the SIP phone on the other end will continue ringing about 4 or 5 times before Asterisk realizes the call has hung up. After doing some searching to find out how to fix this problem, I came across the following page on the asterisk wiki which talks about "Remote Disconnect Supervision": <http://www.voip-info.org/tiki-index.php?page=Asterisk+Disconnect+Superv ision> Before I call Bell and waste the next hour or two trying to find someone who may know something about this feature, I thought I'd send e a message to the list and see if anyone here happens to know whether Bell provides Remote Disconnect Supervision by default on business lines, and if not, who/where I have to call to get this enabled. I'm running Asterisk 1.2.6, Zaptel 1.2.5 with a Sangoma A200 4 port FXO card. I've also got "signalling = fxs_ks" in zapata.conf for all my channels, and "fxsks=1-4" in zaptel.conf Thanks in advance for any help/suggestions. Mike
