[Home]

Summary:ASTERISK-09082: member "inuse" but get a ring
Reporter:Dirk-Michael brosig (dmbrosig)Labels:
Date Opened:2007-03-23 06:24:14Date Closed:2011-06-07 14:07:55
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Applications/app_queue
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:A sip-user (Eyebeam / x-Lite) is member of 2 or more queues. If he accept a call from queue 1 a second call reached him from queue 2, but he is busy at this time. In the show queues the first call.

002          has 0 calls (max 30) in 'leastrecent' strategy (0s holdtime), W:0, C:0, A:0, SL:0.0% within 0s
  Members:
     SIP/sys_005 (dynamic) (In use) has taken no calls yet
  No Callers

001          has 0 calls (max 30) in 'leastrecent' strategy (0s holdtime), W:0, C:0, A:0, SL:0.0% within 0s
  Members:
     SIP/sys_005 (dynamic) (In use) has taken no calls yet
  No Callers

Now comes a call from the second queue...

002          has 1 calls (max 30) in 'leastrecent' strategy (0s holdtime), W:0, C:0, A:0, SL:0.0% within 0s
  Members:
     SIP/sys_005 (dynamic) (Ring+Inuse) has taken no calls yet
  Callers:
     1. SIP/b_003-081ed1f8 (wait: 0:05, prio: 0)

001          has 0 calls (max 30) in 'leastrecent' strategy (0s holdtime), W:0, C:1, A:0, SL:0.0% within 0s
  Members:
     SIP/sys_005 (dynamic) (Ring+Inuse) has taken 1 calls (last was 402 secs ago)
  No Callers

He get a ring from the second queue. That's more than a mistake in a deaf-environment a flusher signaled the call. That affected the current call. The call-limit in sip.conf affected only outgoing calls, but incomming?

Comments:By: Jason Parker (jparker) 2007-05-11 16:34:31

This isn't really an issue, nor something we can easily fix in the code, but you can make configuration changes locally to do so yourself.

You can use a call-limit for that user, or you can use the standard group counting stuff.  It's out of scope for this tracker to get much more specific than that.