[asterisk-bugs] [JIRA] (ASTERISK-26557) Client can't reconnect to a conference with announcements if the client is suddenly killed

Joshua Colp (JIRA) noreply at issues.asterisk.org
Sat Nov 5 14:55:10 CDT 2016


     [ https://issues.asterisk.org/jira/browse/ASTERISK-26557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Colp closed ASTERISK-26557.
----------------------------------

    Resolution: Not A Bug

This is not a bug in Asterisk. There are a few options in both chan_sip and chan_pjsip which can be used to detect that a channel has gone away. One of them is an RTP timeout that will terminate the channel if RTP is not received within a period of time and the other is session timers which sends a SIP request to the other side and if no response is received terminates the channel. Without either of these there is no way for Asterisk to know that the channel has gone away.

> Client can't reconnect to a conference with announcements if the client is suddenly killed
> ------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26557
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26557
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly.
>    Affects Versions: 13.11.2
>         Environment: GNU/Linux Debian Jessie
> Client LinphoneAndroid/3.1.1 (belle-sip/1.4.2)
>            Reporter: Pablo Saavedra
>
> Observed in conferences with announcements. If the client (Linphone for Android, for example) suddenly fails for some reason (can be reproduce doing a power-off of the device during the call, for example) it is not possible the reconnection to the same conference room with the same client anymore.
> I've observed that confbridge doesn't realize about the peer has been disconnected because you still see the channel of the peer in the Asterisk's stats (sip show channelstats) as active. 
> One way to recover from that status is to kick-off manually the related channel to the particular client.
> A relevant thing here is that this only happens in conferences rooms with announcements. The rooms/users without announcements are safe about this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list