Issue with Domains

Status
Not open for further replies.
A

Art Howarth

New Member
Dec 30, 2017
6
0
1
58
Hello!

Have operational FusionPBX/Freeswitch with IP address as domain.

Have created domain via Fusion. Updated DNS records with provider so name resolves.

Able to ping via FQDN and login to Fusion via FQDN.

However devices can only register to IP address domain and not domain created in Fusion.

Tried going through numerous email threads but nothing conclusive.

In log viewer getting:
2017-12-30 18:42:02.082226 [DEBUG] sofia.c:10044 IP 93.115.26.45 Rejected by acl "domains". Falling back to Digest auth.

So I tried to add the FQDN in Access Controls, no difference.

Thoughts?

Thanks in advance!
Art
 
Hello .... one update. Also tried forcing an ACL update after putting the domain in the ACL for domains with allow
Saw this is in log viewer...

2017-12-30 18:58:25.062190 [WARNING] switch_core.c:1610 Cannot locate domain (xxxxxxx mydomain)

Thoughts
 
Do not put the IP in ACL, that is for carriers only.

Have you recreated the extensions under the new domain??
 
Hello,

Thanks for the response. Have removed the acl.

Yes....even created totally different extension numbers in new domain from the IP domain that is working.

Question: Does it matter what level user creates the extensions? Should I login only to that domain to create? What if I create with super-admin?

Just seeing if I am missing something daft here...

Cheers,
Art
 
Hi Art, not an expert on FusionPBX but are you creating the extensions while "viewing/managing" the extension's domain?
 
Hello,

Yup. Even created an admin only account for that domain, so superuser rights would not get in the way.

Thanks!

Cheers,
Art
 
I think I may have stumbled onto something.....

2017-12-30 21:45:48.015569 [WARNING] sofia_reg.c:1792 SIP auth challenge (REGISTER) on sofia profile 'internal' for......

Why is the call coming into Sophia on an internal profile?

How do you associate a domain with an external profile?

Cheers,
Art
 
You do not, it should be on the internal profile. As long as that returns correct auth it should register.
 
For registration sip-phone:
proxy: domain.pbx.com
outbound proxy: ip.ad.dr.es
DNS not supported, registration - OK.
i'm used 12 domains in FusionPBX Cluster

enjoy.
 
Status
Not open for further replies.
Top Bottom