mirror of
				https://github.com/asterisk/asterisk.git
				synced 2025-10-31 02:37:10 +00:00 
			
		
		
		
	res_mixmonitor: MixMonitorMute by MixMonitor ID
While it is possible to create multiple mixmonitor instances on a channel, it was not previously possible to mute individual instances. This change includes the ability to specify the MixMonitorID when calling the manager action: MixMonitorMute. This will allow an individual MixMonitor instance to be muted via id. This id can be stored as a channel variable using the 'i' MixMonitor option. As part of this change, if no MixMonitorID is specified in the manager action MixMonitorMute, Asterisk will set the mute flag on all MixMonitor spy-type audiohooks on the channel. This is done via the new audiohook function: ast_audiohook_set_mute_all. ASTERISK-30464 Change-Id: Ibba8c7e750577aa1595a24b23316ef445245be98
This commit is contained in:
		
				
					committed by
					
						 Friendly Automation
						Friendly Automation
					
				
			
			
				
	
			
			
			
						parent
						
							71a83c128d
						
					
				
				
					commit
					b2e9419961
				
			
							
								
								
									
										17
									
								
								doc/CHANGES-staging/app_mixmonitor_mute_by_id.txt
									
									
									
									
									
										Normal file
									
								
							
							
						
						
									
										17
									
								
								doc/CHANGES-staging/app_mixmonitor_mute_by_id.txt
									
									
									
									
									
										Normal file
									
								
							| @@ -0,0 +1,17 @@ | ||||
| Subject: app_mixmonitor | ||||
| Subject: audiohook | ||||
| Subject: manager | ||||
|  | ||||
| It is now possible to specify the MixMonitorID when calling | ||||
| the manager action: MixMonitorMute.  This will allow an | ||||
| individual MixMonitor instance to be muted via ID. | ||||
|  | ||||
| The MixMonitorID can be stored as a channel variable using | ||||
| the 'i' MixMonitor option and is returned upon creation if | ||||
| this option is used. | ||||
|  | ||||
| As part of this change, if no MixMonitorID is specified in | ||||
| the manager action MixMonitorMute, Asterisk will set the mute | ||||
| flag on all MixMonitor audiohooks on the channel.  Previous | ||||
| behavior would set the flag on the first MixMonitor audiohook | ||||
| found. | ||||
		Reference in New Issue
	
	Block a user