mirror of
				https://github.com/blakeblackshear/frigate.git
				synced 2025-10-27 10:52:11 +01:00 
			
		
		
		
	clarify webrtc for two way talk (#19683)
This commit is contained in:
		
							parent
							
								
									664a6fd0cb
								
							
						
					
					
						commit
						8a01643acf
					
				| @ -43,7 +43,7 @@ The following ports are used by Frigate and can be mapped via docker as required | |||||||
| | `8971` | Authenticated UI and API access without TLS. Reverse proxies should use this port.                                                                                         | | | `8971` | Authenticated UI and API access without TLS. Reverse proxies should use this port.                                                                                         | | ||||||
| | `5000` | Internal unauthenticated UI and API access. Access to this port should be limited. Intended to be used within the docker network for services that integrate with Frigate. | | | `5000` | Internal unauthenticated UI and API access. Access to this port should be limited. Intended to be used within the docker network for services that integrate with Frigate. | | ||||||
| | `8554` | RTSP restreaming. By default, these streams are unauthenticated. Authentication can be configured in go2rtc section of config.                                             | | | `8554` | RTSP restreaming. By default, these streams are unauthenticated. Authentication can be configured in go2rtc section of config.                                             | | ||||||
| | `8555` | WebRTC connections for low latency live views.                                                                                                                             | | | `8555` | WebRTC connections for cameras with two-way talk support.                                                                                                                  | | ||||||
| 
 | 
 | ||||||
| #### Common Docker Compose storage configurations | #### Common Docker Compose storage configurations | ||||||
| 
 | 
 | ||||||
|  | |||||||
| @ -114,7 +114,7 @@ section. | |||||||
| ## Next steps | ## Next steps | ||||||
| 
 | 
 | ||||||
| 1. If the stream you added to go2rtc is also used by Frigate for the `record` or `detect` role, you can migrate your config to pull from the RTSP restream to reduce the number of connections to your camera as shown [here](/configuration/restream#reduce-connections-to-camera). | 1. If the stream you added to go2rtc is also used by Frigate for the `record` or `detect` role, you can migrate your config to pull from the RTSP restream to reduce the number of connections to your camera as shown [here](/configuration/restream#reduce-connections-to-camera). | ||||||
| 2. You may also prefer to [setup WebRTC](/configuration/live#webrtc-extra-configuration) for slightly lower latency than MSE. Note that WebRTC only supports h264 and specific audio formats and may require opening ports on your router. | 2. You can [set up WebRTC](/configuration/live#webrtc-extra-configuration) if your camera supports two-way talk. Note that WebRTC only supports h264 and specific audio formats and may require opening ports on your router. | ||||||
| 
 | 
 | ||||||
| ## Important considerations | ## Important considerations | ||||||
| 
 | 
 | ||||||
|  | |||||||
		Loading…
	
		Reference in New Issue
	
	Block a user