[asterisk-users] Ring/Off-hook in strange state 6

Dimitri Volski dimavo at mailcall.com.au
Thu Jun 28 02:22:03 CDT 2007


Hi,

I had a similar problem when I had signalling set at FXS_KS for my 4 FXS 
port TDM400P card. I've read long time ago that the signalling in 
Australia (where I am) is FXS_LS, so that solved that for me. Try 
different signalling methods, hopefully that will solve your problem.

Apparently, the Digium tech support has a 2 week queue of requests.

Cheers,
Dimitri


Alex Mcdowell wrote:
> Can anybody at least point me in a direction??
>
> On 6/25/07, Alex Mcdowell <mcdowell.alex at gmail.com> wrote:
>   
>> I don't think my cards are bad, but maybe there is a problem with the
>> one. It has been two weeks since I put my ticket in with Digium...and
>> still no word. I am starting to get frustrated.
>>
>> On 6/22/07, Daniel Hazelbaker <daniel at highdesertchurch.com> wrote:
>>     
>>> Alex,
>>>
>>>
>>>       I had this problem with a new TDM2400 card that we purchased.  Specifically I would get that message and then it would pick up the ringing line AND the line next to it.  Basically, lines 1 & 2 had been cross-linked somehow.  After a few weeks of trouble-shooting with Digium tech support they cross-shipped me a new card and the problem (and that message) went away.
>>>
>>>
>>> Daniel Hazelbaker
>>> High Desert Church
>>>
>>>
>>>
>>> On Jun 22, 2007, at 1:22 PM, Alex Mcdowell wrote:
>>>
>>>
>>>
>>> HI I have two servers both of which get this message on one of the lines.
>>>
>>> Ring/Off-hook in strange state 6. The one server seems to be ok with it, but
>>>
>>> the other one when an extension picks up there is no one there and the
>>>
>>> incoming call keeps ringing. I tried to adjust the levels in wcfxo.c like
>>>
>>> someone had suggested, but it didn't do anything. I also upgraded zaptel to
>>>
>>> the latest. 1.2.18 and asterisk is running at 1.2.14. callprogess is set to
>>>
>>> no, as well as busydetect=no. This is a major problem since this box only
>>>
>>> has 1 other line, but at least it works. I can't seem to find much info on
>>>
>>> this issue. I can't believe others haven't run into it.  I started a ticket
>>>
>>> with digium, but I guess they are pretty backed up. Here is what I am
>>>
>>> getting in the CLI:  Thanks for any help -Alex
>>>
>>>     -- Starting simple switch on 'Zap/4-1'
>>>
>>>     -- Executing Wait("Zap/4-1", "1") in new stack
>>>
>>>     -- Executing Answer("Zap/4-1", "") in new stack
>>>
>>>     -- Executing Dial("Zap/4-1", "SIP/4125|20|tr") in new stack
>>>
>>>     -- Called 4125
>>>
>>> Jun 22 13:44:45 WARNING[24296]: chan_zap.c:3926 zt_handle_event:
>>>
>>> Ring/Off-hook in strange state 6 on channel 4
>>>
>>>     -- SIP/4125-09559118 is ringing
>>>
>>> Jun 22 13:44:46 WARNING[24296]: chan_zap.c:3926 zt_handle_event:
>>>
>>> Ring/Off-hook in strange state 6 on channel 4
>>>
>>>     -- SIP/4125-09559118 answered Zap/4-1
>>>
>>>   == Spawn extension (incoming, s, 3) exited non-zero on 'Zap/4-1'
>>>
>>>     -- Hungup 'Zap/4-1'
>>>
>>>     -- Starting simple switch on 'Zap/4-1'
>>>
>>>     -- Executing Wait("Zap/4-1", "1") in new stack
>>>
>>>     -- Executing Answer("Zap/4-1", "") in new stack
>>>
>>>     -- Executing Dial("Zap/4-1", "SIP/4125|20|tr") in new stack
>>>
>>>     -- Called 4125
>>>
>>> Jun 22 13:44:57 WARNING[24303]: chan_zap.c:3926 zt_handle_event:
>>>
>>> Ring/Off-hook in strange state 6 on channel 4
>>>
>>>     -- SIP/4125-09559118 is ringing
>>>
>>> Jun 22 13:44:58 WARNING[24303]: chan_zap.c:3926 zt_handle_event:
>>>
>>> Ring/Off-hook in strange state 6 on channel 4
>>>
>>>     -- SIP/4125-09559118 answered Zap/4-1
>>>
>>>   == Spawn extension (incoming, s, 3) exited non-zero on 'Zap/4-1'
>>>
>>>     -- Hungup 'Zap/4-1'
>>>
>>>     -- Starting simple switch on 'Zap/4-1'
>>>
>>>     -- Executing Wait("Zap/4-1", "1") in new stack
>>>
>>>     -- Executing Answer("Zap/4-1", "") in new stack
>>>
>>>     -- Executing Dial("Zap/4-1", "SIP/4125|20|tr") in new stack
>>>
>>>     -- Called 4125
>>>
>>>     -- SIP/4125-09559118 is ringing
>>>       
>


-- 
This message has been scanned for viruses and
dangerous content by Mail Call antivirus software, and is
believed to be clean.




More information about the asterisk-users mailing list