Yes, I am aware of that. I think it might be easier if TangoPBX or Sangoma were to make a docker tool similar to discourse_docker, to manage each TPBX or FPBX instance easily within VMs
Well not sure about that since FreePBX shouldn’t be run in Docker and it actually is not an advised way to handle a FreePBX instance. Since Sangoma has actively advises against it since they acquired FreePBX, I doubt that making a docker solution is in the cards.
3 Likes
Oh interesting. Didn’t realize that.
I find clients that we convert from an old hybrid system that had SLA have a hard time wrapping their head around the fact that “lines” (and their inherent limitation) don’t exist in modern systems. I remember being reluctant myself years and years ago when I first encountered parking functionality. I couldn’t understand why we needed that when we could just forward a call…. Obviously I get it now.
I had one such conversion just this week as an existing client (medical) bought another practice to merge into theirs and the existing staff came with it. They had an OLD NEC system with just 2 lines.
The existing practice that bought them uses call queues to manage calls which enables them to limit the staff they need answering the phones. The new practice staff just couldn’t wrap their heads around it and thought the phones were broken because they kept ringing. “Why can’t the 2nd call just go to voicemail and we’ll call them back like we always did???” “We never had this many calls before” (yeah, because you only had 2 lines..)
I had to explain how inefficient that was for all parties and show them that the avg wait time in their new queue was under 2 minutes. Then explain if those callers went to vm instead of waiting (less than 2 min) and getting answered, you then had to take more time to listen to the vm, call them back later, maybe get their vm, wait for a callback, maybe they get vm again, wash… rinse… repeat….
What’s this got to do with SLA? my point is I think people want SLA simply because it’s what they were used to and nobody likes change. If the end users are educated on the features of the PBX and how to leverage them to make communications more efficient, they quickly forget about SLA.
Time is better spent educating than trying to re-create a feature that in reality, they want but don’t actually NEED.
- Disable an extension without deleting
- no other way to do this day than removal or changing the secret
- Link extension updates to Userman in some manner
- Changing the extension display name from Joe to Carol leaves the display name in Userman as Joe, same with email changes at the extension level
- Global inbound redirect
- Multiple DIDs need to be modified today if you want to play a message to all callers that the “Office is closed for XYZ” or something like that; it would be nice to send calls to an announcement and then on the defined path to communicate something you want anyone calling into the system to hear
1 Like
I expect there are many examples of cool features that aren’t widely exposed, but one that comes to mind is a backup number to be called should your phone become unregistered.
The system can use follow-me even when it’s disabled under normal circumstances - only to be used when the extension is offline… many users and some admins seem to forget this, or they never knew it existed.
Making items like this more visible in relevant sections of the UI would be a nice addition.
Are you saying follow-me when configured but disabled will route calls to the alternate location if the endpoint goes offline?
This is something I’ve personally needed haha
1 Like
@Ashcor yes , but you need to enable one advanced setting - see below
The more you know…… thanks!!