The media tunneling feature provides uniform client messaging and signaling from team engagement and customer engagement client SDKs.
Avaya SBC supports media tunneling through HTTP proxy which acts as a medium that may change the TLS certificate of the media stream.
Media tunneling provides uninterrupted service when:
A direct media connection path is unavailable between clients and the enterprise infrastructure.
The corporate firewall of the remote customer enterprise blocks media packets and connection to a specific enterprise infrastructure from within another customer enterprise infrastructure.
Avaya SBC does not provide any interworking functionality for media tunnel calls so the topology must be homogenous.
Media tunneling supports:
SHA1 and SHA2 hash algorithms.
The maximum concurrent capacity of tunneled calls supported by Avaya SBC, if you select the Media Tunneling check box under in the EMS web interface.
Remote users that use the HTTPS proxy with SSL inspection mode must whitelist the conferencing server domains in the HTTPS proxy.
In case of a heterogenous environment where HTTPUA clients are behind MIM proxies like Zscalar, SSL Proxy Mode needs to be configured at HTTPUA clients. This triggers a proprietary mechanism of media tunneling which is transparent to any MIM proxies like Zscalar. There is no configuration requirement at Avaya SBC and is adapted dynamically based on client signaling.
