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.

Sign up for GitHub

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

Jump to bottom

Broker generated pjsip configuration file does not resolve all domains #783

Open
spalladino opened this issue Dec 13, 2016 · 0 comments · May be fixed by #793
Open

Broker generated pjsip configuration file does not resolve all domains #783

spalladino opened this issue Dec 13, 2016 · 0 comments · May be fixed by #793
Assignees
@ggiraldez
Labels
bug in progress

Comments

@spalladino
Copy link
Contributor

The broker attempts to DNS resolve all domains to IPs before writing the pjsip_verboice.conf file, though in several cases it is failing to do so (match=testsipclient, for instance).

Decide what we want to do with those cases, and if we leave them as is, ensure that Asterisk is able to correctly resolve them if the broker fails.
@spalladino spalladino added the bug label Dec 13, 2016
ggiraldez added a commit that referenced this issue Jan 27, 2017
@ggiraldez
Add striping to some channel settings values
cfcc3e4 
This should help a bit dealing with user entry errors while configuring
channels. Regarding #783, 2 out of 3 channels which fail to resolve the IP
address of the domain have a whitespace at the start/end of the domain, which
makes the DNS query fail. Plus, we've had authentication errors in the past due
to extra whitespace in the username and password.
@ggiraldez ggiraldez linked a pull request Jan 27, 2017 that will close this issue
Open
@ggiraldez ggiraldez self-assigned this Jan 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ggiraldez ggiraldez

Labels
bug in progress
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Don't configure Asterisk channels whose domain name cannot be resolved instedd/verboice
2 participants
@spalladino @ggiraldez