asterisk users - Aug 2003 - x100P: Ring/off-hook in strange state 6 on channel1

All of a sudden I am getting the following warning "Ring/off-hook in
strange state 6 on channel1" from chan_zap.c and I cannot answer calls. I
can place calls out without a problem though.

Any ideas what can be the problem. I have checked zapata.conf and zaptel.conf
and they both seem fine.

Thanks in advance.
Dan


-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20030826/71e24b7d/attachment.htm

| From: "Dan Fernandez" <danfernandez00@hotmail.com>
| Date: Tue, 26 Aug 2003 16:30:40 -0400
| 
| All of a sudden I am getting the following warning "Ring/off-hook in
| strange state 6 on channel1" from chan_zap.c and I cannot answer calls.
| I can place calls out without a problem though.

I'm having the same problem with current asterisk versions - asterisk
sees the FXO line ringing, and claims to answer it, but doesn't
actually pick up the phone:

    -- Starting simple switch on 'Zap/1-1'
    -- Executing Wait("Zap/1-1", "1") in new stack
    -- Executing Answer("Zap/1-1", "") in new stack
    -- Executing DigitTimeout("Zap/1-1", "5") in new stack
    -- Set Digit Timeout to 5
    -- Executing ResponseTimeout("Zap/1-1", "10") in new
stack
    -- Set Response Timeout to 10
    -- Executing Wait("Zap/1-1", "1") in new stack
    -- Executing BackGround("Zap/1-1", "cs/cs_thank_you") in
new stack
    -- Playing 'cs/cs_thank_you'
WARNING[14351]: File chan_zap.c, Line 2857 (zt_handle_event): Ring/Off-hook in
strange state 6 on channel 1
    -- Executing Goto("Zap/1-1", "ringmain|s|1") in new
stack
    -- Goto (ringmain,s,1)
    -- Executing BackGround("Zap/1-1",
"cs/cs_wait_for_staff") in new stack
    -- Playing 'cs/cs_wait_for_staff'
  == Spawn extension (ringmain, s, 1) exited non-zero on 'Zap/1-1'
    -- Hungup 'Zap/1-1'


If I revert back to my CVS copy from June 1, it works fine.
But the September 10 release code won't answer, and neither
will the current CVS version (or various previous CVS versions).

This card is a couple of months old, and is not the current card - I
haven't received my replacements yet.

I haven't seen anything else in the mailing lists that seems related
to this.  Any suggestions?

Thanks!

John
jsellens@generalconcepts.com

| From: Eric Wieling <eric@fnords.org>
| 
| On Tue, 2003-09-16 at 12:19, John Sellens wrote:
| > I'm having the same problem with current asterisk versions - asterisk
| > sees the FXO line ringing, and claims to answer it, but doesn't
| > actually pick up the phone:
|
| Have your tried setting busydetect=no and callprogress=no in
| /etc/asterisk /zapata.conf?

Thanks Eric - that did the trick.

I think that this change in behaviour is due to this change in
channels/chan_zap.c:

3529c3670
<               if (i->callprogress && CANPROGRESSDETECT(i)
&& i->outgoing) {
---
>               if (i->callprogress && CANPROGRESSDETECT(i)) {
which I think used to allow callprogress only when an outoing call
is being placed (which seems reasonable on the surface - you don't
need callprogress on inbound calls/channels) but now always allows
callprogress.


But the thing I don't understand is, I think both callprogress and
busydetect default to 0/false/no/off in chan_zap.c, and I hadn't
set them earlier in my zaptel.conf file, but they seemed to be
getting set to yes in my case (or at least behaving that way).
Looking at the code, I don't see an obvious way for that to happen.

Oh well, perhaps I am hallucinating and not understanding properly.

Thanks!

John
jsellens@generalconcepts.com