Summary:ASTERISK-00132: Hangup Not Properly Detected / Strange Line State
Reporter:jayson (jayson)Labels:
Date Opened:2003-08-20 11:42:06Date Closed:2011-06-07 14:05:07
Versions:Frequency of
Description:We've got a Vina eLink-216 that our telco provided for terminating their T1 on a site.

We tried to integrate an Asterisk box with a TDM400P.  Eventually this was to become a full fledged phone system.  However, initially we were just setting it up to bounce calls through (ring-ins on channels 1-10, ring out of channels 49-58, channels 10-24 for more lines later, channels 25-48,59-96 to be used for internal phones later).

Quickly a problem arose.  The incoming calls always terminate fine.  Asterisk then hangs up the other channel--or so it thinks.  The Vina (or at least the old PBX attached to it) doesn't think the channel is hung up and stays offhook.

Quickly wedged channels stack up until the the whole system is fine.


I suspect hat this is the Vina rather than the old PBX, as either running ztcfg or yanking the T1 causes all of the channels to unwedge/hangup on the PBX end.

I have tried fxs_gs, fxs_ls, and fxs_ks.  It seems to like fxs_ks the best.  I am confident that this is not PRI or anything exciting like that.  It is just a fractional T1 probably using RBS or something like that.

Asterisk logs some strangeness when this happens too.  I was not able to copy them down when they occurred, but I hope to take the phones down again tonight to test this out.  I will be updating to the newest CVS before this test.

If I remember correctly, the message was something akin to:

Strange ring/off-hook state for channel ? state 6

Any ideas?

Comments:By: jayson (jayson) 2003-08-20 11:45:06

Found it in the log:

File chan_zap.c, Line 2768 (zt_handle_event): Ring/Off-hook in strange state 6 on channel 4

Oddly, this occurs on the incoming lines (not the ones failing to hang up).  Could it be that this strange ring/off-hook state needs to get sent to the Vina to indicate it should hang up?  I'll check tonight to see if this occurs when the call rings in or after the call hangs up.

By: jayson (jayson) 2003-08-20 18:23:29

Here they are:

NOTICE[32788]: File chan_zap.c, Line 4185 (ss_thread): Got event 2 (Ring/Answered)...
NOTICE[37910]: File app_dial.c, Line 495 (dial_exec): Unable to create channel of type 'Zap'
WARNING[37910]: File chan_zap.c, Line 2768 (zt_handle_event): Ring/Off-hook in strange state 6 on channel 4
WARNING[39960]: File chan_zap.c, Line 2768 (zt_handle_event): Ring/Off-hook in strange state 6 on channel 5
WARNING[40985]: File chan_zap.c, Line 2768 (zt_handle_event): Ring/Off-hook in strange state 6 on channel 6
WARNING[42004]: File chan_zap.c, Line 2768 (zt_handle_event): Ring/Off-hook in strange state 6 on channel 7

By: x martinp (martinp) 2003-08-21 14:41:00

what's the version of chan_zap.c ?

"grep chan_zap.c /usr/src/asterisk/channels/CVS/Entires"

By: jayson (jayson) 2003-08-21 14:45:05

/chan_zap.c/1.88/Tue Aug 19 13:27:58 2003//

By: x martinp (martinp) 2003-08-21 14:48:29

can you configure those channels as e&m=1-24 in /etc/zaptel.conf and signalling=em or signalling=em_w in zapata.conf ?

By: jayson (jayson) 2003-08-21 20:26:16

Tried.  That completely broke EVERYTHING (phantom rings, hung channels across the board, general badness).

By: John Todd (jtodd) 2003-09-12 18:31:46

Jayson - any more information on this?

By: x martinp (martinp) 2003-09-21 14:38:17

I think it was on the list you can check if you use callprogres=yes then change it to now and see if that fixes it.

By: jayson (jayson) 2003-10-06 11:32:20

It's on my list to try.

By: x martinp (martinp) 2003-10-06 11:34:20

If that'll help you with your old code then in the recent code you can use callprogress (that issue was solved -> entering some wierd 6 state)

By: Mark Spencer (markster) 2003-10-16 05:59:20

Is this resolved?

By: x martinp (martinp) 2003-10-16 11:56:33

It seems to be resolved however I had one customer with a fresh code that still had it. The problem is that if the callprogress is set to yes we did try to do callprogress detection on incoming calls. Also everything was working fine about 2 months ago and then 'someone' commited the bug.

By: x martinp (martinp) 2003-11-03 16:06:02.000-0600

This should be resolved. The callprogress=yes got broken at one point.

By: jayson (jayson) 2003-11-04 16:31:39.000-0600

Problem persists.  callprogress=no or callprogress=yes with newest CVS.

By: Mark Spencer (markster) 2003-11-04 23:31:22.000-0600

What about callprogress=no and busydetect=no