asterisk users - Jun 2004 - Problem with * not detecting hangup on FXO and VM going into an infinite loop

Hi everybody...

I'm having an odd problem with voice mail on a recent CVS of * where it 
appears not to detect a hangup on FXO and * will keep treating the call 
as new and continue leaving voicemails until the max has been reached.

It will then continue trying to leave voice mails and basically makes 
the system unavailble to any further incoming or outgoing calls on that 
FXO..has anybody seen this and if so how do I fix it?

I've looked around on google and the list archives and it appears that 
there are others with similar problems with most people believing it to 
be a configuration problem. Since I don't see any bugs that have been 
formally posted with this description I think it most likely is...can 
anybody help me determine which option would be causing this behavior? I 
assume its in zapata.conf?

Thanks!
Chris

-- 
It's easy to sit there and say you'd like to have more money.  And I
guess
that's what I like about it. It's easy. Just sitting there, rocking back
and forth, wanting that money.


http://ccicolorado.org
Exceptional Dogs for Exceptional People - Help Out Today!

On Thu, 2004-06-10 at 10:54, Chris Hirsch wrote:
> Hi everybody...
> 
> I'm having an odd problem with voice mail on a recent CVS of * where it
> appears not to detect a hangup on FXO and * will keep treating the call 
> as new and continue leaving voicemails until the max has been reached.
> 
> It will then continue trying to leave voice mails and basically makes 
> the system unavailble to any further incoming or outgoing calls on that 
> FXO..has anybody seen this and if so how do I fix it?
> 
> I've looked around on google and the list archives and it appears that 
> there are others with similar problems with most people believing it to 
> be a configuration problem. Since I don't see any bugs that have been 
> formally posted with this description I think it most likely is...can 
> anybody help me determine which option would be causing this behavior? I 
> assume its in zapata.conf?
If you where on google and saw the same questions, you should have been
able to follow the rabbit further down the hole by playing with the
links at the bottom of the pages google provided. You would have seen
use rant regularly that you need to work just a tad harder to find the
answer. It is there. It is consistently the same problem. 

You lack disconnect supervision. The only way to know the line has been
hungup is to use progress detection and possibly tweak for your
location.
-- 
Steven Critchfield  <critch@basesys.com>

Yup. I came in the other day and noticed the * server holding a line
open on the FXO for several hours, and a high bandwidth stream on the
IAX (I monitor traffic with 'EtherApe' and 'rate'). Someone had
been
doing early morning testing of the system (not yet in production) by
calling the main office number via an * 7-digit rule from a SIP phone
over IAX, and when I tried to call the desk from outside it was indeed
busy! I told * to hang up on the Zap channel, the IAX went quiet and the
desk was free.

Kinda scary. We have a Nortel PBX for office incoming calls, which is
set to a 'night mode' after hours that goes straight to VM, and I was
wondering if the Nortel system was to blame; no doubt the * went to VM
on Nortel during tests and might have hung there. Maybe IAX and SIP
created the problem.

Hasn't happened since. Maybe someone left their SIP phone connected
after they hit VM? Or improperly quit? Maybe Nortel held the channel
open? Why was IAX hot, too? Beats me.

c@  

On Thu, 2004-06-10 at 08:54, Chris Hirsch wrote:
> Hi everybody...
> 
> I'm having an odd problem with voice mail on a recent CVS of * where it
> appears not to detect a hangup on FXO and * will keep treating the call 
> as new and continue leaving voicemails until the max has been reached.
> 
> It will then continue trying to leave voice mails and basically makes 
> the system unavailble to any further incoming or outgoing calls on that 
> FXO..has anybody seen this and if so how do I fix it?
> 
> I've looked around on google and the list archives and it appears that 
> there are others with similar problems with most people believing it to 
> be a configuration problem. Since I don't see any bugs that have been 
> formally posted with this description I think it most likely is...can 
> anybody help me determine which option would be causing this behavior? I 
> assume its in zapata.conf?
> 
> Thanks!
> Chris