Summary:	ASTERISK-08112: Transfers are not bridging properly
Reporter:	John Lange (johnlange)	Labels:
Date Opened:	2006-11-10 17:59:52.000-0600	Date Closed:	2006-12-11 13:56:22.000-0600
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/Transfers
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) attdxfercrash_console01.txt ( 1) verbosedebug.txt
Description:	When you connect the destination leg of a trasnfer with the original caller, Asterisk displays a huge number of Packet2Packet bridging messages (verbose 99). I don't believe these grow longer over time as a freshly started asterisk has the same issue. This is on an attended transfer using the phone feature buttons (not the Asterisk features.conf). The phones are SPA 942s. ****** ADDITIONAL INFORMATION ******    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268    -- Packet2Packet bridging SIP/2049757113x1-08201c88 and SIP/2049757116x1-08206268
Comments:	By: Olle Johansson (oej) 2006-11-12 08:46:34.000-0600 You always need to add a SIP debug log (please read the bug guidelines). Thanks! By: John Lange (johnlange) 2006-11-13 12:44:01.000-0600 sip debug doesn't work in current 1.4 branch: No such command 'sip debug' By: Olle Johansson (oej) 2006-11-13 13:16:21.000-0600 Then read the docs... "sip debug on" I believe works now. By: John Lange (johnlange) 2006-11-13 13:46:15.000-0600 Ok, two files uploaded. First is a crash from an attended xfer. "console.txt" is a transfer with sip debug enabled, verbose 99. By: Serge Vecher (serge-v) 2006-11-17 10:06:36.000-0600 ok, there is no debug output (see item 2) 1) Prepare test environment (reduce the amount of unrelated traffic on the server -- the notify from linksys); 2) Make sure your logger.conf has the following line:   console => notice,warning,error,debug 3) restart Asterisk with the following command:   'asterisk -Tvvvvvdddddgc | tee /tmp/verbosedebug.txt' 4) Enable SIP transaction logging with the following CLI commands: set debug 4 set verbose 4 sip debug on 5) Attach verbosedebug.txt to the issue. By: Serge Vecher (serge-v) 2006-11-20 15:32:40.000-0600 hmm, interesting ... I did notice that you are using NAT even though traffic seems to be within the private network. What happens if you disable nat? By: Joshua C. Colp (jcolp) 2006-12-04 13:18:22.000-0600 Would it be possible to gain access to the box where this is happening so I can examine stuff and put in debugging information? Thanks. By: wlloyd (wlloyd) 2006-12-04 23:07:15.000-0600 I can confirm that there is something going on.  I'm running a predictive dialer applicaiton on a svn update from today (yes rc3 not trunk) and after enough calls asterisk crashes hard.  It just dies with no messages except the last line is a Packet2Packet line above. It's something todo with canreinvite=yes. the server crashes withing an hour when yes.  When I make canreinvite=no the server seems stable. I've run trunk and the same issue happens. This is the first time I've tried canreinvite=yes in a long time. By: Serge Vecher (serge-v) 2006-12-05 08:25:28.000-0600 wlloyd: can you please email file at jcolp @t digium dot com to arrange for access to the server, if possible. By: John Lange (johnlange) 2006-12-06 16:33:47.000-0600 file: I was testing this on my laptop which is generally not attached directly to the internet and in any case I'd rather not give away root on it. In the coming weeks I will be depolying a new server and there may be an oportunity to let you access that one. What surprises me though is that you are not able to reproduce this on your own test system? Regarding canreinvite; All of my devices are set to =no and the problem still happens just the same. However it may be related to having nat=yes on a non-nat system as serge-v mentions but I have not had time to bring the test system back to life and may not have time again until the new year but will do my best. By: wlloyd (wlloyd) 2006-12-09 10:00:24.000-0600 jculp was on my machine and looked at core file.  Says he knows the issue.  Not sure what's happened since then.  I'd love to try a patch if avail. -bill By: Joshua C. Colp (jcolp) 2006-12-11 13:56:21.000-0600 Fixed in 1.4 as of revision 48381 and trunk as of revision 48383. (Should be at least). If this is still an issue please reopen with the crash/console output and I'll try my best. Peace!