[asterisk-bugs] [JIRA] (ASTERISK-23949) Bridge/0xb75254f-in Bridge/0xb75254f-out channels did not hanguped after call hanguped

hk hk (JIRA) noreply at issues.asterisk.org
Wed Jul 2 06:12:56 CDT 2014


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

hk hk commented on ASTERISK-23949:
----------------------------------

hi in case in which  single user in confbridge 
and user kick hangup or leave , then no Bridge/XXXXXXXXXXXXX-in and Bridge/XXXXXXXXXXXXX-Out  issue has been solved .
But 
Case: Multiple users in confbridge the agian
 Bridge/XXXXXXXXXXXXX-in and Bridge/XXXXXXXXXXXXX-Out ramining after All user hangup.
why ? any clue ? Any suggestion ?


> Bridge/0xb75254f-in  Bridge/0xb75254f-out channels did not hanguped after call hanguped
> ---------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-23949
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23949
>             Project: Asterisk
>          Issue Type: Information Request
>      Security Level: None
>          Components: Applications/app_confbridge
>    Affects Versions: 11.5.1
>            Reporter: hk hk
>            Assignee: hk hk
>
> Centos 6
> Asterisk 11.5.1 
> app:Confbridge
> file:app_confbridge.c
> ===============================
> issue :
> Bridge/0xb75254f channels did not hanguped after call hanguped .
> note1:After call hangup ast_bridge_change_state :2 which means Hangup 
> note2:Patch also note working 
> steps:
> 1)Nornal user Join 
> 2)Hangup the Call.
> kick_conference_participant(struct conference_bridge *bridge, const char *channel)
> myhost*CLI> confbridge kick 585261 SIP/500-00000000
> ===============================
> //---After 1st call start and join conference bridge ---//
> myhost*CLI> core show channels
> Channel              Location             State   Application(Data)             
> Bridge/0xb75254f4-in s at default:1          Up      (None)                        
> SIP/500-00000000     s at confbrindge-room:60 Up      MyConfbridge(585261,,adminuser
> ConfBridgeRecorder/c s at default:1          Up      (None)                        
> Bridge/0xb75254f4-ou s at default:1          Up      (None)                        
> 4 active channels
> 1 active call
> 1 call processed
> //---log----//
> ====Inside bridge_bridgedchannel ====[2014-06-25 14:59:51] NOTICE[24968][C-00000001]:
>  chan_bridge.c:82 bridge_bridgedchannel: ====Inside bridge_bridgedchannel ====� 
>    -- <Bridge/0xb75254f4-input> Playing 'confbridge-leave.slin' (language 'en')
>     --
>   inside handle_conf_user_leave  : USER_OPT_WAITMARKED 
>  �    -- 
>   CONF_STATE_INACTIVE.c insidsec  leave_waitmarked  
>     -- 
>  ##### inside  conf_change_state 
>  �    -- 
>  Changing conference '585261' state from INACTIVE to EMPTY 
> bridging.c:1227 ast_bridge_remove: ===remove bridge channel using func ast_bridge_change_state ===�  
>  -- inside  ast_bridge_change_state : arg1cursteat:0 arg2newstate:2 �    --
>   final  ast_bridge_change_state :2 �    -- 
>     -- Stopped music on hold on SIP/500-00000000
>     -- <SIP/500-00000000> Playing 'conf-kicked.ulaw' (language 'en')
> //----------//
> myhost*CLI> confbridge list
> Conference Bridge Name           Users  Marked Locked?
> ================================ ====== ====== ========
> 585261                               1      1 unlocked
> //---log of After Call Hangup----// 
> myhost*CLI> confbridge list
> Conference Bridge Name           Users  Marked Locked?
> ================================ ====== ====== ========
> myhost*CLI> core show channels
> Channel              Location             State   Application(Data)             
> Bridge/0xb75254f4-in s at default:1          Up      (None)                        
> Bridge/0xb75254f4-ou s at default:1          Up      (None)                        
> 2 active channels
> 0 active calls
> 1 call processed



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



More information about the asterisk-bugs mailing list