Ghost Calls: Ring/Off-hook in strange state 6 on channel X

In searching for answers I found bug 5304 had the same symptoms 10 months ago. First answer is echo and fuzz. Hangup and it rings back with a dial tone when answered.

Any one know how serge-v ended up handling this issue.

0005304: zt_handle_event: Ring/Off-hook in strange state 6 on channel X
Description For several months, we are experiencing “ghost calls” on our Asterisk system. By ghost call I mean an incoming call that is not originated from telco (as per telco). There are two variants of suchs calls (as experienced on receiving end): 1) dead silence 2) dialtone. Such calls are always associated with “Ring/off-hook in strange state 6 on channel X” reported on Asterisk console.

tdm2400 with 12 channels

Asterisk 1.2.10 built by root @ on a i686 running Linux on 2006-08-22 05:25:00 UTC

zaptel-1.2.9.1

[zaptel.conf]
fxsks=1-7
fxsks=9,11,12
loadzone=us
defaultzone=us

Note 8 and 10 are missing. I am having problems with those channels. I am not using them to avoid a grounding issue noted by the telco.

;zapata.conf
;------------------
[trunkgroups]
[channels]
language=en
usecallerid=no
hidecallerid=no
callwaiting=no
restrictcid=no
;usecallingpres=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=128
echocancelwhenbridged=no
echotraining=no
rxgain=3.0
txgain=5.0

musiconhold=default

;FXO interface
group=1
context => incoming
signalling => fxs_ks ;FXS (Kewl Start)
channel => 1-4

group=3
context => detail
signalling => fxs_ks ;FXS (Kewl Start)
channel => 5

group => 2
context => bdc
signalling => fxs_ks ;FXS (Kewl Start)
channel => 6,7,9,11

-- Starting simple switch on 'Zap/9-1'
-- Executing Answer("Zap/9-1", "") in new stack
-- Executing Dial("Zap/9-1", "SIP/503&SIP/504|40||rtT") in new stack
-- Called 503
-- Called 504
-- SIP/503-09a8ad78 is ringing
-- SIP/504-09a96908 is ringing
-- Zap/11-1 answered SIP/501-09a79fc0

Nov 15 21:28:37 WARNING[12133]: chan_zap.c:3922 zt_handle_event: Ring/Off-hook in strange state 6 on channel 9
– Starting simple switch on ‘Zap/7-1’
– Executing Answer(“Zap/7-1”, “”) in new stack
– Executing Dial(“Zap/7-1”, “SIP/503&SIP/504|40||rtT”) in new stack
– Called 503
– Called 504
– SIP/503-09a7cef8 is ringing
– SIP/504-09a82408 is ringing
– SIP/503-09a8ad78 answered Zap/9-1
– SIP/504-09a82408 answered Zap/7-1
== Spawn extension (bdc, s, 2) exited non-zero on ‘Zap/9-1’
– Hungup ‘Zap/9-1’
– Starting simple switch on ‘Zap/9-1’
– Executing Answer(“Zap/9-1”, “”) in new stack
– Executing Dial(“Zap/9-1”, “SIP/503&SIP/504|40||rtT”) in new stack
– Called 503
– Called 504
– SIP/503-09a87918 is ringing
– SIP/504-09a99228 is ringing
Nov 15 21:28:55 WARNING[12152]: chan_zap.c:3922 zt_handle_event: Ring/Off-hook in strange state 6 on channel 9
== Spawn extension (bdc, s, 2) exited non-zero on ‘Zap/7-1’
– Hungup ‘Zap/7-1’
– SIP/503-09a87918 answered Zap/9-1
== Spawn extension (bdc, s, 2) exited non-zero on ‘Zap/9-1’
– Hungup ‘Zap/9-1’
– Hungup ‘Zap/11-1’
== Spawn extension (trunkdial_bdc, 92480580, 1) exited non-zero on ‘SIP/501-09a79fc0’
– Starting simple switch on ‘Zap/9-1’
– Executing Answer(“Zap/9-1”, “”) in new stack
– Executing Dial(“Zap/9-1”, “SIP/503&SIP/504|40||rtT”) in new stack
– Called 503
– Called 504
– SIP/503-09a79fc0 is ringing
– SIP/504-09a8ad78 is ringing
Nov 15 21:29:04 WARNING[12166]: chan_zap.c:3922 zt_handle_event: Ring/Off-hook in strange state 6 on channel 9
– SIP/504-09a8ad78 answered Zap/9-1
== Spawn extension (bdc, s, 2) exited non-zero on ‘Zap/9-1’
– Hungup ‘Zap/9-1’

Have your tried setting busydetect=no and callprogress=no in
/etc/asterisk /zapata.conf?

bugs.digium.com/view.php?id=5304

Hi

This looks like an issue with the leads.

I have noted that Digium fxo and fxs hardware is FAR more reliable if only the center 2 pins are connected. ie a 2 way lead. it looks like pins 2 and 5 of the rj11 socket interfere someway.
for example in the wireing for the US and UK

US

co *
1 1
2 2
3–3
4–4
5 5
6 6

and UK

also add callprogress=no as above

co *
1 1
2 - 2
3 -3
4 -4
5 - 5
6 6

I forgot to mention the only thing that changed was the Telco. We switched from McLeod to Qwest for our POTs lines. Another weird item was we had to introduce a pause in the dialing to make sure we got a line every time. now we have 9wXXX-XXXX.

It is a TDM2400, so it is an amphenol connector not an RJ-11. Thanks for the tip though!

I do not have callprogress=no or detectbusy=no. I will try them.

This is an intermittent problem, so we don’t have much to go on.

Thanks!

aj