[Home]

Summary:ASTERISK-00064: Crashes when AgentCallbackLogin type agent is called and answers the call (before # is pressed)
Reporter:Adam Goryachev (adamg)Labels:
Date Opened:2003-08-08 11:48:18Date Closed:2003-08-09 14:37:12
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Applications/app_queue
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I have just setup a test for AgentCallbackLogin as follows:
extensions.conf:
[dispatchlogin]
exten => *1,1,AgentCallbackLogin(1001|@dispatchlogin) ; to logout use empty ext like # then hangup
exten => 1001,1,Dial,Modem/g1:90402078431|14|mt ; Dial extension...

agents.conf:
agent => 1001,1234,Adam Goryachev

queues.conf:
member => Agent/1001,3

(This is the only member in this queue)

There are two main phones involved, connected as follows:
Home phone ext 650/651
This is connected to a ata186, which connects to a local asterisk, which has a switch statement to connect over IAX2 (on a 64kbps ISDN connection) to a second asterisk which has the above configs.

The second phone is my mobile, asterisk dials out over the ISDN4Linux chan_i4l_modem interface.

I use the 651 to dial *1, login with password, enter extension 1001, and am told that it all worked and goodbye. I hangup and dial back in again to a extension which is added to the queue and sit on hold. Asterisk then attempts to call the mobile, the mobile rings, I answer, and asterisk immediately crashes before I have a chance to press anything etc.

****** ADDITIONAL INFORMATION ******

details from gdb and core file:
#0  0x40026195 in pthread_mutex_unlock () from /lib/i686/libpthread.so.0
(gdb)
(gdb) bt
#0  0x40026195 in pthread_mutex_unlock () from /lib/i686/libpthread.so.0
#1  0x4528a81a in local_hangup (ast=0x8114ad8) at chan_local.c:96
#2  0x08058d8d in ast_do_masquerade (original=0x810fef0) at channel.c:1909
#3  0x08056e10 in ast_read (chan=0x810fef0) at channel.c:1008
#4  0x41ab9a3b in agent_read (ast=0x8112ed0) at chan_agent.c:231
ASTERISK-1  0x08057137 in ast_read (chan=0x8112ed0) at channel.c:1084
ASTERISK-2  0x41f69f6b in wait_for_answer (qe=0x454b31fc, outgoing=0x810fcc0, to=0x454b3148, allowredir_in=0x454b314c, allowredir_out=0x454b3150,
   allowdisconnect=0x454b3154, digit=0x454b315b "") at app_queue.c:486
ASTERISK-3  0x41f6accb in try_calling (qe=0x454b31fc, options=0x454b3312 "t", announceoverride=0x0, url=0x0) at app_queue.c:759
ASTERISK-4  0x41f6bd15 in queue_exec (chan=0x8105d30, data=0x454b373c) at app_queue.c:1128
ASTERISK-5  0x0805efc6 in pbx_exec (c=0x8105d30, app=0x80f4a00, data=0x454b373c, newstack=1) at pbx.c:388
ASTERISK-6 0x08060b5a in pbx_extension_helper (c=0x8105d30, context=0x8105e80 "remote", exten=0x8105f74 "s", priority=6,
   callerid=0x80cafc8 "\"Home 1\" <650>", action=1) at pbx.c:1135
ASTERISK-7 0x080617fe in ast_pbx_run (c=0x8105d30) at pbx.c:1619
ASTERISK-8 0x0806753f in pbx_thread (data=0x8105d30) at pbx.c:1835
ASTERISK-9 0x40024fef in pthread_start_thread () from /lib/i686/libpthread.so.0

cvs update about 30 minutes before this report is submitted

Any other details needed, please let me know
Comments:By: Mark Spencer (markster) 2003-08-08 14:35:00

Already fixed in CVS.