Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proxy cannot communicate with b2bua if transports=sips:* is specified #192

Open
skhrshin opened this issue Aug 7, 2024 · 2 comments
Open

Comments

@skhrshin
Copy link

skhrshin commented Aug 7, 2024

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

  1. Configure proxy with b2bua, specifying transports=sips:*
  2. Connect to proxy from client
  3. 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.

@Failxxx
Copy link
Contributor

Failxxx commented Sep 11, 2024

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.

Sincerely,
Félix

@skhrshin
Copy link
Author

I see.

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".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants