On an environment which supports both IPv4 and IPv6, b2bua sip-bridge mode passes IPv6 address to the upstream SIP servers. If they can send IPv6 packets, b2bua can hear RTP stream but it is unreachable if they can't.
Environment
Flexisip 2.3.4 on Debian GNU/Linux bookworm
Steps to reproduce
Configure b2bua-server with sip-bridge mode
Set up sip-bridge so that it would connect to SIP server which doesn't support IPv6 (like Docker container with default settings)
Call from the client connecting to the proxy so that b2bua would bridge to that SIP server.
Expected behavior
Audio from the callee reaches the caller.
Actual behavior
The caller can hear nothing from the callee.
Remarks
The cause of this issue seems to be the address of b2bua passed to the upstream SIP server.
In my case, the SIP server I want b2bua to bridge to was on a Docker container, so I needed to configure IPv6 for the container as workaround.
Overview
On an environment which supports both IPv4 and IPv6, b2bua sip-bridge mode passes IPv6 address to the upstream SIP servers. If they can send IPv6 packets, b2bua can hear RTP stream but it is unreachable if they can't.
Environment
Flexisip 2.3.4 on Debian GNU/Linux bookworm
Steps to reproduce
Expected behavior
Audio from the callee reaches the caller.
Actual behavior
The caller can hear nothing from the callee.
Remarks
The cause of this issue seems to be the address of b2bua passed to the upstream SIP server.
In my case, the SIP server I want b2bua to bridge to was on a Docker container, so I needed to configure IPv6 for the container as workaround.