|Summary:||ASTERISK-07113: Agent hung after getting call from Manager API Originate|
|Reporter:||Mark Hagler (hagler)||Labels:|
|Date Opened:||2006-06-06 22:39:50||Date Closed:||2006-07-12 14:27:12|
|Environment:||Attachments:||( 0) agents.conf|
( 1) queues.conf
|Description:||Here's a strange one, but reproducable on two boxes:|
Roundrobin queue with two Agents (configs attached). Agents logged in to Local/700 and Local/778.
exten => 571,1,Queue(markq|r|||60)
Calls work fine if you call 571 directly from another phone, agent takes the call, hangs up, agent gets another call just fine.
I have another setup where I launch a call via Manager API from external when a RT ticket comes in and I want it to call into the queue and play a recording to get somebody to look at it:
Channel: Local/571@default #this is the queue extension
Callerid: RT Notify <999>
Which shoudl call around the queue and the connect the Agent with this relatively simple action:
exten => start,1,Wait(1)
exten => start,2,Playback(rt-ricket-notify)
exten => start,3,Hangup
This works once, call rings around the queue, agent answers call, it plays the audio file, hangs up.
After that, the agent that answered and heard the Playback is hosed, and also the entire queue hangs when a call hits that agent again. This applies even if the next call into the queue is a real call (not the automated 'outcall' deal).
Show channels indicates that it's trying to dial the agent's callback, but no SIP INVITE ever went to the client after this. Console shows that it executes Queue and then hangs entirely.
== Manager 'mark' logged on from 172.16.1.9
-- Executing Queue("Local/571@default-64dc,2", "markq|r|||60") in new stack
rickets*CLI> show channels
Channel Location State Application(Data)
Local/571@default-64 571@default:1 Ring Queue(markq|r|||60)
Local/571@default-64 s@default:1 Down (None)
Agent/1111 s@stations:1 Down (None)
Local/3700@stations- 3700@stations:1 Ring (None)
Local/3700@stations- s@stations:1 Down (None)
IAX2/wings-3 571@default:1 Ring Queue(markq|r|||60)
6 active channels
2 active calls
Using stock 1.2.9 code here...
|Comments:||By: Serge Vecher (serge-v) 2006-06-30 13:43:40|
Is this reproducible in latest 1.2 svn? There were a couple of changes to chan_local that went in after 1.2.9 release.
By: Serge Vecher (serge-v) 2006-07-12 14:26:59
no response for two weeks from hagler. Feel free to reopen if you can reproduce this bug with latest 1.2 branch.