Sorry about the last message, it was just plain wrong. Reading these traces is making my eyes cross.
I ran a system call trace on the freeswitch process and identified the poison
message from there, then looked back into a merged.xml trace (attached for this
instance of the crash, same issue but different instance as the merged.xml I
sent previously) to find the message.
It appears as if the problem is the 'ringing' message sent from sipXproxy back
to freeswitch after transferring the call from the AA by hitting 200# (missing
the 'Contact' field resulting in the SEGV).
Here's the message as seen by freeswitch:
24331 recvmsg(16, {msg_name(16)={sa_family=AF_INET, sin_port=htons(5060),
sin_addr=inet_addr("192.172.252.163")}, msg_iov(1)=[{"NOTIFY
sip:[email protected]:15060;transport=udp SIP/2.0\r\nVia: SIP/2.0/UDP
192.172.252.163;branch=z9hG4bK-XX-07b432D2B4jqGVTeYjHwe2SPrw\r\nVia:
SIP/2.0/UDP 192.172.252.21:5061;branch=z9hG4bK-b6a7a6c0\r\nFrom: \"SMITH,A\"
<sip:[email protected]>;tag=6100d25bbf738d26o1\r\nTo:
<sip:[email protected]>;tag=UetjXjKHN2m0B\r\nCall-Id:
[email protected]\r\ncseq: 102 NOTIFY\r\nMax-Forwards:
20\r\nEvent: refer\r\nUser-Agent: Linksys/SPA3102-5.1.10(GW)\r\nContent-Length:
21\r\nContent-Type: message/sipfrag;version=2.0\r\nDate: Sun, 03 Jan 2010
20:15:24 GMT\r\n\r\nSIP/2.0 180 Ringing\r\n", 570}], msg_controllen=0,
msg_flags=0}, 0) = 570
and I think this lines up with this entry in merged.xml:
</branchNode>
<branchNode>
<branchIdSet>
<branchId>z9hG4bK-XX-07b432D2B4jqGVTeYjHwe2SPrw</branchId>
<branchId>z9hG4bK-b6a7a6c0</branchId>
</branchIdSet>
<time>2010-01-03T20:15:24.401509Z</time>
<source>d3.foo21.com-SipXProxy</source>
<destination>192.172.252.163:15060</destination>
<sourceAddress>d3.foo21.com-SipXProxy</sourceAddress>
<destinationAddress>192.172.252.163:15060</destinationAddress>
<transactionId>102,[email protected],6100d25bbf738d26o1,UetjXjKHN2m0B</transactionId>
<method>NOTIFY</method>
<frameId>48 sipXproxy.xml:51447</frameId>
<message><![CDATA[NOTIFY
sip:[email protected]:15060;transport=udp SIP/2.0^M
Via: SIP/2.0/UDP 192.172.252.163;branch=z9hG4bK-XX-07b432D2B4jqGVTeYjHwe2SPrw^M
Via: SIP/2.0/UDP 192.172.252.21:5061;branch=z9hG4bK-b6a7a6c0^M
From: "SMITH,A" <sip:[email protected]>;tag=6100d25bbf738d26o1^M
To: <sip:[email protected]>;tag=UetjXjKHN2m0B^M
Call-Id: [email protected]^m
Cseq: 102 NOTIFY^M
Max-Forwards: 20^M
Event: refer^MUser-Agent: Linksys/SPA3102-5.1.10(GW)^MContent-Length: 21^M
Content-Type: message/sipfrag;version=2.0^M
Date: Sun, 03 Jan 2010 20:15:24 GMT^M
^M
SIP/2.0 180 Ringing^M
]]></message>
-Eric
PS: I had to use a tar/bz2 wrapper to get around some sort of virus scanner
brain damage at my mail provider.
merged.tar.bz2
Description: BZip2 compressed data
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
