How to config DSS keys on Yealink handsets from FreePBX
-
@360col said in How to config DSS keys on Yealink handsets from FreePBX:
@jaredbusch said in How to config DSS keys on Yealink handsets from FreePBX:
@bnrstnr said in How to config DSS keys on Yealink handsets from FreePBX:
You could set them in the phone's web interface. That's how I did ours, granted we only have ~20 phones, so it was a set it once kind of thing that took like 3 min per phone.
EDIT: Didn't notice the "from FreePBX" bit. Sorry
But still endpointmanager is only for the face template. Anything you sent their applies to all devices. To set a specific key for a specific extension can only be done from the UCP and only if you have permission to see that extension in UCP.
I'm trying set common keys for a group of extensions that are site / department specific. Multiply by many such groups. Fro my curiosity can a template be applied to a group of extensions or only to specif models of handsets?
From what I've learned / read so far FreePBX is not the best for running multi sites as you'll run into problem eventually.
FreePBX is not a multi-tenant solution.
If that’s what you have going on here you just need to stop and shut it all down because it’s wrong it’s going to break and it is going to kill you later. -
@360col said in How to config DSS keys on Yealink handsets from FreePBX:
From what I've learned / read so far FreePBX is not the best for running multi sites as you'll run into problem eventually.
Multi-sites, no problem. Multi-tenant, not supported.
-
Its more a multi sites than muti tenant. However what we are using make it more like multi tenant.
I got onto this after the whole thing has been started by someone else (who hasn't though it through / sold the wrong thing and in experience in this) and used for a while. I'm trying to tweak it to work as best as I can.
For the moment I need to get it working best I can. Until I can think about it more and or convince higher up to migrate to a better solution.
Best I start another thread on what might have been the best setup for our scenario.
-
@360col said in How to config DSS keys on Yealink handsets from FreePBX:
Its more a multi sites than muti tenant. However what we are using make it more like multi tenant.
I got onto this after the whole thing has been started by someone else (who hasn't though it through / sold the wrong thing and in experience in this) and used for a while. I'm trying to tweak it to work as best as I can.
For the moment I need to get it working best I can. Until I can think about it more and or convince higher up to migrate to a better solution.
Best I start another thread on what might have been the best setup for our scenario.
Consider what this might be costing you per month, moving to another solution might be a simple change of vendor, not a new cost.
-
What is meant by the term multi-tenant?
-
@jmoore said in How to config DSS keys on Yealink handsets from FreePBX:
What is meant by the term multi-tenant?
Individual businesses owned under a single umbrella. They all need a service (phones for example) and rather than have X-difference phone systems. You simplify the entire system, with 1 system that supports multiple tenants.
All with their own call routes, numbers, dialing plans etc.
-
@dustinb3403 said in How to config DSS keys on Yealink handsets from FreePBX:
You simplify the entire system, with 1 system
@jmoore Its all about minimizing support cost and consistency.
-
Ok cool thanks, that makes sense
-
@dustinb3403 said in How to config DSS keys on Yealink handsets from FreePBX:
@jmoore said in How to config DSS keys on Yealink handsets from FreePBX:
What is meant by the term multi-tenant?
Individual businesses owned under a single umbrella. They all need a service (phones for example) and rather than have X-difference phone systems. You simplify the entire system, with 1 system that supports multiple tenants.
All with their own call routes, numbers, dialing plans etc.
Not what it means.
Multi-tenant has nothing to do with business ownership.
https://en.wikipedia.org/wiki/Multitenancy
The term "software multitenancy" refers to a software architecture in which a single instance of software runs on a server and serves multiple tenants. A tenant is a group of users who share a common access with specific privileges to the software instance. With a multitenant architecture, a software application is designed to provide every tenant a dedicated share of the instance - including its data, configuration, user management, tenant individual functionality and non-functional properties. Multitenancy contrasts with multi-instance architectures, where separate software instances operate on behalf of different tenants.
FreePBX has no way to separate or dedicate a share of the design. It is all a big plot of extensions, ring groups, etc.
For a single large company like the OP has, there is not an obvious requirement for multitenancy, but it would be better for keeping such a massive system organized.
Some examples.
FreePBX cannot have two extensions 1337. FusionPBX could with a separate tenant.
FreePBX can only have a single 0 for operator extension. A multitenant solution can have each tenant with a 0 for operator option. -
@jaredbusch Ok thanks for the explanation
