You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When proxy is configured with b2bua, it attempts to communicate with b2bua server when a call arrives, but it fails if proxy is not listening any ports other than TLS.
Environment
Flexisip 2.3.4 on Debian GNU/Linux bookworm
Steps to reproduce
Configure proxy with b2bua, specifying transports=sips:*
Connect to proxy from client
Call somewhere
Expected behavior
proxy can communicate with b2bua server.
Actual behavior
Communication fails with the following error.
flexisip-debug-nta: selecting scheme sip
flexisip-debug-nta outgoing create: no transport protocol
Remarks
As workaround, I had to specify transports=sip:127.0.0.1 sips:* instead.
The text was updated successfully, but these errors were encountered:
Hello @skhrshin,
Thank you for taking the time to report a problem with Flexisip.
Indeed, Flexisip (proxy) cannot send requests to other clients/servers using a transport that is not defined in the global/transports parameter. This is expected behavior.
I would be nice if some friendly error message is emitted even if log-level is set to "error", whereas the error I reported is recorded only when log-level is set to "debug".
Overview
When proxy is configured with b2bua, it attempts to communicate with b2bua server when a call arrives, but it fails if proxy is not listening any ports other than TLS.
Environment
Flexisip 2.3.4 on Debian GNU/Linux bookworm
Steps to reproduce
transports=sips:*
Expected behavior
proxy can communicate with b2bua server.
Actual behavior
Communication fails with the following error.
Remarks
As workaround, I had to specify
transports=sip:127.0.0.1 sips:*
instead.The text was updated successfully, but these errors were encountered: