domains are case sensitive - but caps are not honoured when creating a domain

V

Voipy

New Member
Feb 5, 2026
16
0
1
56
Hi

We took over another voip business a while ago. They, for no particular reason, used capitals in the first part of a domain name. So CAPS.domain.com. Prior versions of Fusion would save it as such. Later versions do not.

Freeswitch treats domains as case sensitive so when a phone registers with CAPS.domain.com, the domain on the server has to match this. However, creating a domain like that doesn't get saved with the capitals, it saves it in lower case.

The result of it is that we have not been able to easily move those clients over to our platform because our version of Fusion does the same. If I create the domain directly in the DB then it keeps the caps but the worry has been that it will overwrite this at some point so we haven't gone that route. The customers have a whole range of different phones so autoprovisioning is not an easy option here either. First prize is to just create the domain in the way it was on the old fusion that they had (and we now run).

I had hoped that FSPBX would honour the caps but it doesn't either, which is no doubt a legacy from Fusion. Is there any chance of getting that changed so that when capitals are used they remain that?
 
If your plan is to export the data and import it to FS PBX, why do you need to keep the domain name the same? This is a perfect time to adopt the unified name convention that uses only lowercase.
 
Hi - no the issue is that there are 1200 phones out there that are registering to the domain with the capitals. We can replicate their PBXs easily enough and point the domain to a new IP - and the customer won't even know they are on a new pbx. If we cannot replicate the capitals, it means contacting the customers who are all over the place to change their phone configs. We don't even know what phones they have, Mac addresses, etc so the only easy way is to just keep the caps. And given the fact that freeswitch treats it as case sensitive, I reckon the correct way is to also do so in the gui? Notwithstanding that nobody I know has ever used upper case - except for this crowd.
 
We simplified things in FS PBX. You register against your main domain and pass the tenant domain in the header. It's a unified way of doing things. If you must, you can still make tenant domains routable, but it's not a hard requirement, and it makes things a lot easier in the long run. For example, it avoids the issue you are dealing with right now.

However, our support team will be happy to assist you with making the domain case-sensitive as a one-off if you have no other choice. If you reach out to us when you're ready to get that started, it'll be a quick adjustment.
 
Hi

I fully agree with the approach of simplifying it, and any new customer we would pass the tenant domain in the header - that makes sense. I just don't see an easy way of dealing with the legacy thing that we sit with so once we get to that point we'll tackle that one with the help of your support team then. Thank you!

I am moving along nicely so far. No doubt I will fire off some more posts as it's better to keep topics in their own thread, but I am already pretty convinced of making the jump!
 
You must log in or register to reply here.
Top Bottom