Summary:ASTERISK-13258: queues fail to recognize already logged in local channel using \n member
Reporter:Rene Mendoza (renemendoza)Labels:
Date Opened:2008-12-22 12:55:23.000-0600Date Closed:2008-12-22 17:06:29.000-0600
Versions:Frequency of
Description:Affects: asterisk and

When a local channel with the \n construct tries to log in a second time, the dynamic queue will allow it if the channel has taken at least one call

if the channel has not taken any call, it will properly be logged in/out every time, if the channel does not use the \n construct it will properly be logged in/out every time even after taking calls

This bug is producing several different problems
1) a member is logged multiple times, (one time per login attempt)
2) at least the first logged in interface will have its name changed, the \n will be taken out of the name and such it prevents to be logged out except manually via the asterisk CLI


Connected to Asterisk currently running on acuarius (pid = 26473)

701          has 0 calls (max unlimited) in 'rrmemory' strategy (1s holdtime), W:0, C:7, A:0, SL:100.0% within 10s
     Local/1667@agentes/n (Local/1667@agentes) (dynamic) (Not in use) has taken 1 calls (last was 13 secs ago)
     Local/1667@agentes/n (dynamic) (Not in use) has taken no calls yet
  No Callers

exten => s,1,Noop
exten => s,n(login),AddQueueMember(${ARG1},Local/${CALLERID(num)}@agentes/n)
exten => s,n,Playback(agent-loginok)
exten => s,n,Hangup()
exten => s,login+101,Playback(agent-alreadyon&vm-goodbye)
exten => s,n,Hangup()
exten => i,1,Goto(s,1)
exten => t,1,Goto(s,1)

exten => s,1,Noop
exten => s,n(logout),RemoveQueueMember(${ARG1},Local/${CALLERID(num)}@agentes/n)
exten => s,n,Playback(agent-loggedoff)
exten => s,n,Hangup()
exten => s,logout+101,Playback(vm-no&in-the-queue&vm-goodbye)
exten => s,n,Hangup()
exten => i,1,Goto(s,1)
exten => t,1,Goto(s,1)

Comments:By: Mark Michelson (mmichelson) 2008-12-22 16:15:58.000-0600

This looks like it's the exact same issue as seen in issue ASTERISK-13162. Take a look at the comment history and you should see the instructions for the patches which are attached there.

I'm going to mark these two issues as related.

By: Rene Mendoza (renemendoza) 2008-12-22 16:44:09.000-0600

the first patch did the trick for me. thanks

By: Mark Michelson (mmichelson) 2008-12-22 17:03:47.000-0600

Excellent. What I'm going to do is close this issue as a duplicate of ASTERISK-13162. The actual fix won't be committed until I hear back from the reporter of that issue so that I'll know if the second patch will need to be committed as well as the first.