Summary:ASTERISK-01285: Double link events while linking two channels
Reporter:maciejka (maciejka)Labels:
Date Opened:2004-03-24 17:44:10.000-0600Date Closed:2011-06-07 14:00:39
Versions:Frequency of
Description:While connecting two channels manager apparently gets two 'Link' events:

Event: Link
Channel1: IAX[kamyk@]/44
Channel2: SIP/kamyk-acbe
Event: Unlink
Channel1: IAX[kamyk@]/44
Channel2: SIP/kamyk-acbe
Event: Link
Channel1: IAX[kamyk@]/44
Channel2: SIP/kamyk-acbe

If this sequence of Link,Unlink,Link events is correct, how then one is to be sure that connection has been setup?
Comments:By: Mark Spencer (markster) 2004-03-24 18:43:33.000-0600

Are you on IRC or somewhere I can ask in real time some of the more obvious questions like "Does it unlink a second time when it's over?" and "what makes you think this bug is a 'block' bug as opposed to 'minor' for example?"  Note that the link/unlink events correspond to whe ast_bridge is called.  It is possible for an ast_bridge to be temporarily interrupted by an event such as a control frame, and then continued by the calling application.  Anyway find me on IRC in the next 24 hours or I'm just going to chalk this up to a misunderstanding of link/unlink.

By: maciejka (maciejka) 2004-03-25 05:44:32.000-0600

It does unlink when hungup.

My assumption is that manager events are for monitoring asterisk activity and out of defined events 'link' event means connection setup between two channels.

Double link/unlink for single connection confuses manager clinet or makes it more complicated than necessary.

If link/unlink mean something different, than other kind of event seems necessary to indicate connection setup/teardown.

'Block' bug because is blocks manager clients developement. If 'block' is for something else please change it to minor.

My email is maciejka at tiger.com.pl. I will try to reach You at IRC today and tommorow. Later I will be offline for a week.

By: Mark Spencer (markster) 2004-03-25 11:34:45.000-0600

The link is a general way of indicating that two channels are talking to one another.  You could go bya answer/hangup if that's what you care about, presumably.

A "block" means that it causes Asterisk to become unresponsive, but not actually segfault or in some other way terminate.  

I'm going to go ahead and close this out since it's not even a bug at all, and you might put in a new "feature request" if you can *much more clearly* define what it is that you want an event for.