Search results

OK! That does the trick. It has to be set under Advanced > Group Manager then click on the permissions for Superadmin and scroll down to Ring Groups Then click the check box next to Caller-ID Name Prefix to enable. Save, log out and log back in to see the field.

On current FusionPBX, the caller-id name and number, if specified, are what is sent out when the ring group rings an external number. It is not a caller-id prefix for incoming calls to ring group members. That is exactly how it works in FS PBX.

Correct. FreePBX does it but I don't see an option in the GUI for FS PBX or FusionPBX. You should submit an enhancement request on the FS PBX issues list at https://github.com/nemerald-voip/fspbx/issues

I think I found where you can add a CID prefix for your ring group. You do it on the advanced tab of the Phone Numbers. In this case on the inbound DID for the ring group, you can add a prefix to the incoming caller-id. It isn't quite the same as adding a prefix for all calls to the ring...

I agree. The box is much wider than necessary for the extension descriptions so why not make the box smaller and put the "Add Selected Members" button to the right side of the box instead of under it. @pbxgeek might want to look at that for a minor redesign of the screen. I've added this to...

When you are adding a new member to the ring group, select the extension(s) and it will still show other extensions. Click the uparrow on the upper right of the selection to close it. Then click the Add Selected Members button to add it to your ring group. Finally, click Save at the bottom...

I didn't realize the post was in FS PBX. I was looking at new posts. We'll have to see what he has to say. I know caller-id works through the ring group with current FS PBX unless his carrier is disallowing it. So @jeroentjed will need to comment on his version of FS PBX as well.

What version of FusionPBX are you running? I'm on 5.5.7 and do not have the issue with the number not being forwarded to the cell phone from the inbound caller..

My request was that when an extension is created that a mailbox not be created unless you opted for it during extension creation. The bulk creation is an even bigger issue. You might want to post it as a feature request for FS PBX here: https://github.com/nemerald-voip/fspbx/issues

I had brought this exact issue earlier about a voice mailbox being created for every extension. I believe @pbxgeek was considering how to address that. There are many instances where there should never be a voice mailbox created for an extension.

Neither my Debian-12 system or my Debian-13 system, both on FSPBX 1.4.2 have an issue. The show the page correctly for me.

Here is my outbound route list and the dialplan generated is below:

I am using FusionPBX 5.5. Your screen shot looks like you are manually editing in the dialplan manager instead of creating with the outbound routes screen. I also set up separate outbound routes for 911, other 3-digit service codes, local 7-digit, toll 10/11 digit, toll-free, and international...

Have you tried building an outbound route using the selectable option of "International"? Also, did you enable international calling on Voip.ms per their instructions?

Many in the US are using Acrobits or other white-label versions of Acrobits such as the offering from ClearlyIP's Clearly Anywhere softphone. In my experience, I've seen little or no uptake for Ringotel in the FreePBX/Asterisk world or amongst any proprietary PBX systems.. I believe Ringotel is...

I found that out myself as I tried to spin up a duplicate machine. I don't know if anyone has mentioned this to the OP @marc8lange that he needs to add or give an option to add the .env to the backup/restore process since the original thread is closed to comment.

The cloud PBX is always on and working regardless of local problems that could shut down an on-prem PBX such as hurricanes, fallen trees on your trunk feeds, etc. If your whole office suffers a disaster or loses power or internet connectivity, your cloud PBX is still there. It can still take...

Did you set up the inbound destination number under the Dialplan > Phone numbers? It looks like you tried to create a manual inbound route. In FreePBX, you'd set it under inbound routes. On FS PBX, you have to set up using Dialplan > Phone Numbers and then, on that screen, route that number...

Well, I re-imaged my cloud VM, re-installed FS PBX, the followed the script on this thread: https://www.pbxforums.com/threads/backup-restore.8702/#post-35209 It worked and restored the original FS PBX configuration to the new host. I changed the domain name, rebooted, and all is OK so far.