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

[Pablo Saavedra (JIRA)]

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

Pablo Saavedra commented on ASTERISK-26557:
-------------------------------------------

The issue looks pretty linked to {{announce_user_count}} announce. Disabling it the client can rejoin into the room even the if the previous channel is still active and registered in the room.

{panel:title=Diff|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1|bgColor=#FFFFCE}
#!diff
diff --git a/confbridge.conf b/confbridge.conf
index e773065..0426eed 100644
--- a/confbridge.conf
+++ b/confbridge.conf
@@ -144,7 +144,7 @@ admin=no
 music_on_hold_when_empty=yes
 music_on_hold_class=default
 quiet=no
-announce_user_count=yes
+announce_user_count=no
 announce_user_count_all=no
 announce_only_user=no
 dsp_drop_silence=yes
{panel}

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