[Asterisk-bugs] [Asterisk 0010166]: The device state of this queue member, SIP/XXXXX, is still 'Not in Use' when it probably should not be!
noreply at bugs.digium.com
noreply at bugs.digium.com
Tue Jul 10 08:34:32 CDT 2007
The following issue has been REOPENED.
======================================================================
http://bugs.digium.com/view.php?id=10166
======================================================================
Reported By: bcnit
Assigned To: file
======================================================================
Project: Asterisk
Issue ID: 10166
Category: Applications/app_queue
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
Asterisk Version: 1.4.6
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: Yes
Request Review:
======================================================================
Date Submitted: 07-10-2007 02:05 CDT
Last Modified: 07-10-2007 08:34 CDT
======================================================================
Summary: The device state of this queue member, SIP/XXXXX, is
still 'Not in Use' when it probably should not be!
Description:
This appears to be related to bug http://bugs.digium.com/view.php?id=0008580.
sip, queues and queue members are being driven from realtime (MySQL).
I get several warnings when queueing calls:
-- Executing [s at cust-in:44] Queue("SIP/103-095182f0", "0844304|n") in
new stack
[Jul 10 07:49:00] WARNING[6677]: translate.c:163 framein: no samples for
gsmtolin
-- Started music on hold, class 'default', on SIP/103-095182f0
-- SIP/101-09522e00 is ringing
-- SIP/101-09522e00 is ringing
-- SIP/101-09522e00 is ringing
[Jul 10 07:49:02] WARNING[4029]: chan_sip.c:3140 update_call_counter:
Inringing for peer '101' < 0?
-- SIP/101-09522e00 answered SIP/103-095182f0
-- Stopped music on hold on SIP/103-095182f0
[Jul 10 07:49:02] WARNING[6677]: app_queue.c:2646 try_calling: The device
state of this queue member, SIP/101, is still 'Not in Use' when it probably
should not be! Please check UPGRADE.txt for correct configuration
settings.
== Spawn extension (cust-in, s, 44) exited non-zero on
'SIP/103-095182f0'
I have followed the instructions in UPGRADE.txt (see below).
The result is that calls are offered to handsets which are already on a
call and this has broken a 1.2 based application when ported to 1.4.
======================================================================
----------------------------------------------------------------------
bcnit - 07-10-07 08:34
----------------------------------------------------------------------
OK. I take your point.
In that case, the bug is that the warning messages are, at best,
misleading.
In addition, given that this situation is likely to occur in a high call
volume environment (where realtime is being used), the warning messages are
likely to swamp any other output.
May I request that some thought be given to not displaying the warning
messages if the device in question is defined in the realtime configuration
and rtcachefriends=no?
Issue History
Date Modified Username Field Change
======================================================================
07-10-07 08:34 bcnit Status closed => feedback
07-10-07 08:34 bcnit Resolution not fixable => reopened
07-10-07 08:34 bcnit Note Added: 0067052
======================================================================
More information about the Asterisk-bugs
mailing list