Summary:	ASTERISK-13432: channel.c: ast_indicate_data: Unable to handle indication -1
Reporter:	Benny Amorsen (amorsen)	Labels:
Date Opened:	2009-01-22 10:11:51.000-0600	Date Closed:	2009-01-30 14:59:44.000-0600
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Applications/app_dial
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I keep seeing this error: [Jan 22 17:01:32] WARNING[12478]: channel.c:2958 ast_indicate_data: Unable to handle indication -1 for 'SIP/10.0.1.100-b698da38' This bug looks very similar to 14078 (which was reported for 1.4.x) but 14078 does not mention which patch fixed the issue, so I can't see if it's supposed to be fixed in 1.6.1. ****** ADDITIONAL INFORMATION ****** I am running 1.6.1 beta 4 + the patches for issues 14110 and 14180.
Comments:	By: Mark Michelson (mmichelson) 2009-01-23 15:22:28.000-0600 It appears that revision 166535 of branch 1.6.1 should have the fix for this. This revision was made after the tagging of 1.6.1-beta4. Run the following command from your 1.6.1-beta4 source directory to get your version of Asterisk patched, and see if the problem persists. <pre> # svn diff http://svn.digium.com/svn/asterisk/branches/1.6.1@166534 http://svn.digium.com/svn/asterisk/branches/1.6.1@166535 | patch -p0 </pre> Edit: Tried to make it so Mantis won't format the URLs oddly Edit2: Didn't work :( By: Benny Amorsen (amorsen) 2009-01-26 09:54:26.000-0600 I can't actually access origsvn.digium.com, even for reading. I have (just now) received permission from management to sign the License Agreement, so I did, in case that makes things easier. By: Mark Michelson (mmichelson) 2009-01-26 10:13:28.000-0600 Ugh, sorry about that. I have updated the URLs in my previous note to point to places that you have read access to. By: Benny Amorsen (amorsen) 2009-01-30 12:52:05.000-0600 Sorry, it took a while, the servers we have the problem on are actually in semi-production... Anyway, the patch works great! By: Mark Michelson (mmichelson) 2009-01-30 14:59:43.000-0600 Great, I'll close the issue then! Thanks for the feedback!