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

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233432#comment-233432 ] 

Asterisk Team commented on ASTERISK-26557:
------------------------------------------

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.

> 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)