Queue problem : Caller leaving the queue instead being on hold

Hello everyone,

I have a problem with my queues : when I have an extension in a queue with one agent connected and this one is on pause.

Then I put an other extension in an other queue, where the same
paused agent is connected, but this queue has a lower weight than the
other one.

When I unpaused the agent connected on these 2 queues, he is called
by the one situaded on the higher weight queue, until now, it’s normal,
but the other one situaded on the other queue is hanged up and that is
not normal.

In order to understand where the problem come, I have put for each
output options a log component, but nothing appears on the Asterisk log.

Here is the log on the Asterisk server:

SIP/531007 is the agent connected on 2 queues.

SIP/531002 is the caller located on the queue with 0 weight.

SIP/531001 is the caller located on the queue with 5 weight.

unpaused interface 'SIP/531007'
 == Using SIP RTP TOS bits 184
 == Using SIP RTP CoS mark 5
-- Called SIP/531007
-- Exiting on time-out cycle
-- Executing [1@ext-queues:41] Macro("SIP/531002-000002a6", "blkvm-clr,") in new stack
-- Executing [s@macro-blkvm-clr:1] Set("SIP/531002-000002a6", "SHARED(BLKVM,SIP/531002-000002a6)=") in new stack
-- Executing [s@macro-blkvm-clr:2] Set("SIP/531002-000002a6", "GOSUB_RETVAL=") in new stack
-- Executing [s@macro-blkvm-clr:3] MacroExit("SIP/531002-000002a6", "") in new stack
-- Executing [1@ext-queues:42] Gosub("SIP/531002-000002a6", "sub-record-cancel,s,1()") in new stack
-- Executing [s@sub-record-cancel:1] Set("SIP/531002-000002a6", "__REC_POLICY_MODE=") in new stack
-- Executing [s@sub-record-cancel:2] ExecIf("SIP/531002-000002a6", "1?Return()") in new stack
-- Executing [1@ext-queues:43] Set("SIP/531002-000002a6", "__NODEST=") in new stack
-- Executing [1@ext-queues:44] Set("SIP/531002-000002a6", "_QUEUE_PRIO=0") in new stack
-- Executing [1@ext-queues:45] Set("SIP/531002-000002a6", "__CWIGNORE=") in new stack
-- Executing [1@ext-queues:46] Set("SIP/531002-000002a6", "QDEST=") in new stack
-- Executing [1@ext-queues:47] Set("SIP/531002-000002a6", "VQ_DEST=") in new stack
-- Executing [1@ext-queues:48] GotoIf("SIP/531002-000002a6", "1?:,,") in new stack
-- Auto fallthrough, channel 'SIP/531002-000002a6' status is 'UNKNOWN'
-- Executing [h@ext-queues:1] Macro("SIP/531002-000002a6", "hangupcall,") in new stack
-- Executing [s@macro-hangupcall:1] GotoIf("SIP/531002-000002a6", "1?theend") in new stack
-- Goto (macro-hangupcall,s,3)
-- Executing [s@macro-hangupcall:3] ExecIf("SIP/531002-000002a6", "0?Set(CDR(recordingfile)=)") in new stack
-- Executing [s@macro-hangupcall:4] Hangup("SIP/531002-000002a6", "") in new stack
== Spawn extension (macro-hangupcall, s, 4) exited non-zero on 'SIP/531002-000002a6' in macro 'hangupcall'
== Spawn extension (ext-queues, h, 1) exited non-zero on 'SIP/531002-000002a6'
-- SIP/531007-000002a7 is ringing

So I want to know why the one in the lower weight queue is hanged up and not in hold?

Thank you for your answers.