[asterisk-bugs] [Asterisk 0015158]: Message: "Unable to handle indication 3"

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15158 
====================================================================== 
Reported By:                madkins
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15158
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            have not tried
Severity:                   tweak
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.0 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-05-19 13:29 CDT
Last Modified:              2009-06-12 11:23 CDT
====================================================================== 
Summary:                    Message: "Unable to handle indication 3"
Description: 
I get this when I connect to a Cisco 7905g.  I have a core asterisk server,
then an asterisk dev pbx, then the phone.  So the phone is not directly
connected to the asterisk that is throwing the error.

====================================================================== 

---------------------------------------------------------------------- 
 (0106339) madkins (reporter) - 2009-06-12 11:23
 https://issues.asterisk.org/view.php?id=15158#c106339 
---------------------------------------------------------------------- 
Our configuration files may not be really useful.  The action is all
occurring in the AGI daemon.  I should note that the phone connects to an
Asterisk instance configured as a PBX which is used to route test calls
between various development and qa environments.  Each of those is an
instance of the main Asterisk / AGI setup specified above.

The behavior in question can occur on either the PBX or a core instance. 
I was just fooling around and it looks like I don't see it on the PBX when
I let the core Asterisk make the outbound call, but I do see it on the PBX
when I use it to call from one SIP phone to another (not invoking the core
Asterisk / AGI instance at all).  I'll post the PBX configuration. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-12 11:23 madkins        Note Added: 0106339                          
======================================================================