asterisk users - Jan 2004 - FW: [Asterisk-Dev] Strange bells in voicemail and voicemailmain ?

Hi,

I've sent this to asterisk-dev recently, but seen no comments. Has anyone
else experienced this behaviour ? I've made a complete clean checkout of CVS
code, and it still happens....
> -----Original Message-----
> I've just made a new update from cvs on my devel box to play 
> with, and I noticed that I get console bells when I start the 
> voicemail app and asterisk seems to hang the channel.
> 
> (I'm running asterisk non-detached in a screen, so my screen 
> starts blinking madly and becoming unusable, have to kill the 
> window and start again)
> 
> Further debugging:
> 
> I'm moved CVS back as far as 20/12 and it still doesn't work, 
> so I'm curious as to what could be causing this...
Thanks,

Florian

On Fri, 2004-01-02 at 08:31, Florian Overkamp wrote:
> Hi,
> 
> I've sent this to asterisk-dev recently, but seen no comments. Has
anyone
> else experienced this behaviour ? I've made a complete clean checkout
of CVS
> code, and it still happens....
> 
> > -----Original Message-----
> > I've just made a new update from cvs on my devel box to play 
> > with, and I noticed that I get console bells when I start the 
> > voicemail app and asterisk seems to hang the channel.
> > 
> > (I'm running asterisk non-detached in a screen, so my screen 
> > starts blinking madly and becoming unusable, have to kill the 
> > window and start again)
> > 
> > Further debugging:
> > 
> > I'm moved CVS back as far as 20/12 and it still doesn't work, 
> > so I'm curious as to what could be causing this...
> 
> Thanks,
> 
> Florian
> 
Hi Florian,

Yes I have seen this with a fresh checkout of 12/31 cvs. It happened
with the second call mostly. First call would usually succeed without
the console bell ringing. I started * in an xterm with asterisk -cgvvvv
Also tried to reboot the box to see if that made it go away (maybe
ztdummy had gone nuts) but that didn't make a difference. The previous
release that (for me) did not have that issue was from 24/12. No idea
what's causing it but it is annoying enough to unplug the speaker.

Regards,
Patrick