[asterisk-dev] chan_iax "ghost" channel confusion

[David Vossel]

----- "Russell Bryant" <russell at digium.com> wrote:

> First, I suppose calling it "channels" to begin with was a bad idea,
> 
> as it is the root cause of the confusion.  "channels" in this context,
> 
> or in the case of "sip show channels", is different than the Asterisk
> 
> channel concept.  These CLI commands show all exchanges currently in
> 
> progress at the protocol level.
> 
> 
> 
> So, with that said, we should definitely leave these types of entries
> 
> in the output.  To clarify their meaning, how about we add a new
> 
> column to the output that indicates what type of IAX2 message started
> 
> this dialog? (Do we call them dialogs in IAX2?)  So, it would say NEW,
> 
> POKE, REGREQ, etc.  I also like the "Last Message" item in the
> 
> chan_sip output.


Would the new column be considered a new feature or a bug fix?  This really needs to be clarified in both 1.4 and 1.6.x.  I don't believe the last message sent or the start message is stored in the iax2_pvt yet.  I suppose checking iax2_peer *peerpoke, iax2_registry *reg, and ast_variable *vars/*iaxvars would let us know if its a poke, registry, or new message.  Would this be sufficient?

~Vossel