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

Jigasi does not resolv DNS of SIP Server #400

Open
SchaeVHS opened this issue Feb 28, 2022 · 1 comment
Open

Jigasi does not resolv DNS of SIP Server #400

SchaeVHS opened this issue Feb 28, 2022 · 1 comment

Comments

@SchaeVHS
Copy link

SchaeVHS commented Feb 28, 2022

Dear Devs,
many thanks for jitsi!

In my local docker-compose deployment I can't connect to my freeswitch (voip provider),
because Jigasi does not resolve the DNS entry.
I'm pretty sure it is a Jigasi bug and not docker-related:

[email protected]
JIGASI_SIP_SERVER=174.5.43.3
--> works, no problems

JIGASI_SIP_URI=username@docker-alias
JIGASI_SIP_SERVER=docker-alias
--> does not work.

Error log:
Jigasi 2022-02-28 19:10:20.130 SEVERE: [35] impl.protocol.sip.ProtocolProviderServiceSipImpl.register().444 No address found for ProtocolProviderServiceSipImpl(SIP:username@docker-alias)

I also tested inside the docker container:
I can ping docker-alias, I get correct result with dig. And also port docker-alias:5060is reachable inside the jigasi container, so the only thing left is that jigasi does not use the system resolv config?

@SchaeVHS
Copy link
Author

SchaeVHS commented Feb 28, 2022

I found the issue:
Jigasi is searching a SRV record, which is usually not provided by local deployments or docker.

If you set the jigasy proxy system, it falls back to normal DNS queries and works.
For docker this is reachable by setting the following in the .env file:

JIGASI_SIP_PORT=5060
JIGASI_SIP_TRANSPORT=UDP

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

No branches or pull requests

1 participant