Hi,<br><br>Can anyone tell me at what time a realtime member with dadhi channel will enter the state Ringing?<br><br>All other realtime DAHDI queue members on my asterisk system will always have the state (Unknown) no matter if it is ringing or not.<br>
But this one queue/queuemember sometimes sudden enters the state Ringing, and never leaves.<br><br>Am I the only one experiencing this?<br><br>Håkon<br><br><br><div class="gmail_quote">2010/3/9 Håkon Nessjøen <span dir="ltr"><<a href="mailto:haakon@avelia.no">haakon@avelia.no</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>
<br>
This is the output from queue show 28:<br>
<br>
47 (DAHDI/g0/12345678) (realtime) (Ringing) has taken no calls yet<br>
<br>
Why is the devicestate "Ringing" when no channels is calling this<br>
number, and the queue says "has taken no calls yet"?<br>
<br>
Is it picking up the general state of a random channel on g0 in dahdi?<br>
Or what is happening? It only seems to happen with this particular<br>
queue/queuemember.<br>
<br>
And it may seem like asterisk doesn't always tro to call this channel<br>
when people enter the queue, because of the erroneous "Ringing" state.<br>
<br>
Even when asterisk has 0 channels in use, this state can be "Ringing"<br>
for this member.<br>
<br>
This is on Asterisk 1.6.1.2.<br>
<br>
Might this be a (former?) bug in device-state or app_queue?<br>
<font color="#888888"><br>
Håkon<br>
</font></blockquote></div><br>