1 | | WebRtc AEC support is added in ticket #1888. However, building WebRtc separately has a few drawbacks: |
2 | | - Following the recommended steps to build WebRtc, it is required to download the entire project which is large in size (approximately 6 GB), while we actually only require a small portion of it (namely, the AEC component). |
3 | | - The latest version of WebRtc has some modifications which is incompatible with our implementation. Thus, we can only use the version circa October 2015 or before. |
| 1 | WebRTC AEC support is added in ticket #1888. However, building WebRTC separately has a few drawbacks: |
| 2 | - Following the recommended steps to build WebRTC, it is required to download the entire project which is large in size (approximately 6 GB), while we actually only require a small portion of it (namely, the AEC component). |
| 3 | - The latest version of WebRTC has some modifications which is incompatible with our implementation. Thus, we can only use the version circa October 2015 or before. |
9 | | 1. By default, WebRtc will always be built automatically. This automatic build can be disabled via configure script param {{{--disable-webrtc}}}. |
10 | | 1. if you want to use external WebRtc, specify {{{--with-external-webrtc}}} and set header/library search paths via CFLAGS and LDFLAGS environment variables. See [https://trac.pjsip.org/repos/ticket/1888#Forotherarchitectures ticket #1888] for more details as to which libraries are required. |
| 9 | 1. By default, WebRTC will always be built automatically. This automatic build can be disabled via configure script param {{{--disable-webrtc}}}. |
| 10 | 1. if you want to use external WebRTC, specify {{{--with-external-webrtc}}} and set header/library search paths via CFLAGS and LDFLAGS environment variables. See [https://trac.pjsip.org/repos/ticket/1888#Forotherarchitectures ticket #1888] for more details as to which libraries are required. |