[Home]

Summary:ASTERISK-07843: Core Dump in ? on Hangup After Transfer
Reporter:Douglas Garstang (dgarstang)Labels:
Date Opened:2006-09-29 16:31:59Date Closed:2006-10-02 08:59:33
Priority:CriticalRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I have three Polycom SIP appearances.

9220370 and 3254101 are registered to xxx.187.140.167
3254103 is registered to xxx.187.140.169

9220370 calls 3254101, which is handled by xxx.187.140.167. DUNDi is used to lookup the location of 3254101. For reasons that I will skip here, each DUNDi node has itself as a peer. So 9220370 goes and connects to itself via the IAX path supplied by the DUNDi lookup.

3254101 then does a blind SIP transfer, and transfers 9220370 to 3254103. Now, 3254103 is registered to xxx.187.140.169, so another DUNDi lookup is done, and this time an IAX path to xxx.187.140.169 is returned.

The call between 9220370 and 3254103 is bridged. When 3254103 disconnects the call, the asterisk process on xxx.187.140.169 core dumps straight away.

Here's the backtrace from the core file.

#0  0xb7784f9c in socket_process (thread=0x8193500) at chan_iax2.c:7598
7598            if (iaxs[fr->callno]->last < fr->ts) {
(gdb)
(gdb) bt
#0  0xb7784f9c in socket_process (thread=0x8193500) at chan_iax2.c:7598
#1  0xb778ef7b in iax2_process_thread (data=0x8193500) at chan_iax2.c:7653
#2  0x080ec859 in dummy_start (data=0x81855a0) at utils.c:538
#3  0xb7f6d294 in start_thread () from /lib/libpthread.so.0
#4  0xb7da032e in clone () from /lib/libc.so.6
(gdb)

The problem is reasonably reproducable.

I'm not sure what files are needed as the Bug Guidelines don't mention what to do with core files.

Comments:By: Douglas Garstang (dgarstang) 2006-09-30 16:09:50

Can someone close this. It was opened by mistake.
By: Clod Patry (junky) 2006-09-30 18:28:23

closed