Posted: Fri May 01, 2009 10:16 pm Post subject: [asterisk-dev] chan_iax "ghost" channel confusion
Hey!
Sometimes "iax2 show channels" displays channels with "(None)" listed as the channel name.
*CLI> iax2 show channels
Channel Peer Username ID (Lo/Rem) Seq (Tx/Rx) Lag Jitter JitBuf Format
(None) 10.24.69.220 (None) 03859/00000 00001/00000 00000ms 0000ms 0040ms unknow
1 active IAX channel
To the user this is somewhat deceiving as it appears to be some sort of memory leak (http://bugs.digium.com/view.php?id=14207). In reality it is usually either a pending poke or registration request, typically to a peer that is unreachable. If the peer is unreachable, these "channels" may appear indefinitely as Asterisk attempts to register with them.
Since they are not channels, it seems odd to me that registrations and pokes are listed at all. Chan_sip does the exact same thing, but it produces far less confusion since they are listed as dialogs and the last message is visible as a REGISTER.
*CLI> sip show channels
Peer User/ANR Call ID Format Hold Last Message Expiry
10.24.16.230 (None) 2b7659b59e65342 0x0 (nothing) No Rx: REGISTER
1 active SIP dialogs
What should be done in chan_iax to clarify this. Should there just be a note at the bottom of the output explaining why these nameless "channels" may exist?
~Vossel
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
Posted: Sat May 02, 2009 4:40 am Post subject: [asterisk-dev] chan_iax "ghost" channel confusion
On May 2, 2009, at 1:03 AM, David Vossel wrote:
Quote:
Sometimes "iax2 show channels" displays channels with "(None)"
listed as the channel name.
*CLI> iax2 show channels
Channel Peer Username ID (Lo/Rem)
Seq (Tx/Rx) Lag Jitter JitBuf Format
(None) 10.24.69.220 (None) 03859/00000
00001/00000 00000ms 0000ms 0040ms unknow
1 active IAX channel
Quote:
What should be done in chan_iax to clarify this. Should there just
be a note at the bottom of the output explaining why these nameless
"channels" may exist?
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.
--
Russell Bryant
Digium, Inc. | Senior Software Engineer, Open Source Team Lead
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.com & www.asterisk.org
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
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
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
Posted: Tue May 05, 2009 1:04 pm Post subject: [asterisk-dev] chan_iax "ghost" channel confusion
On May 4, 2009, at 5:04 PM, David Vossel wrote:
Quote:
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?
I think this would work, yes.
I'm fine with this being done in 1.4, as clarifying what is going on
will help prevent future bug reports due to confusion.
--
Russell Bryant
Digium, Inc. | Senior Software Engineer, Open Source Team Lead
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.com & www.asterisk.org
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum