Search results

@6EbULhkEoM I don't see why not. But I won't recommend it. Let's encrypt certs expire every 3 months, which means you will have to apply a new certificate and restart FreeSWITCH every 3 months.

@Jeff w How much RAM do you have on this server? You need at least 2 GB to compile without running out of resources.

Navigate to the Extensions list page, then click on the three dots and select SIP Credentials.

@vuthy09 It doesn't check any of those variables when the session is set up. It writes all domains to the session variable as long as you have the domain_switch permission set to true for the user. The paid member feature probably modifies that in some capacity as per MrOscured.

If you switch to FS PBX, a nice modern dashboard for Freeswitch built on top of FusionPBX, you will have this functionality out of the box.

Wow I was looking for the same answer for months. I really thought this was a freeswitch bug. My variables were empty.

I've implemented that in FS PBX using multi-site admin. It took some modifications to the original FusionPBX to make it all work. Now, certain users can be assigned permissions to switch between allowed domains.

Mine is a bit older, but this is an example of brilliance and power that must be used carefully. If there was a bug at some point, there are no guarantees that another bug won't make an appearance at some point. This one caused me and my clients a very big headache one morning.

Typically, redundancy is achieved via database replication and some file replication. Then, you point your main DNS record to the primary server and set up some way of failing over to the other server in case the first one doesn't respond. After that, you need to decide if you are failing over...

@mdriaz Glad it's working out for you. I'm playing with some FS events right now and wonder why they are not used more. When executed correctly, they are magical when it comes to achieving some goals. I can't wait to see your app.

That brilliance and power come with a lot of bugs. I ran the update script the other day, and it restored all disabled ring group destinations. I spent half of my morning hearing complaints from the clients until we manually disabled them all again. Be careful to just run it that script at will.

Maybe try overriding the caller ID before parking the call? Then, in theory, it should go back to that destination instead.

@mdriaz As we discussed at the beginning of this thread, the only way to truly catch every scenario is to catch a FreeSWITCH event. Everything else has its own dial string, and it won't work. You should look into that route.

Queues need to be reloaded via the CLI command. Saving info in DB is not enough. When you hit save on the portal, it does it in the background.

To be honest, I don't know if there is an answer to this. Maybe someone else knows something about it. It's possible that there is no solution and that's why all push servers exist separately. However, fail_on_single_reject=false could do the trick if you manage to wake and reregister...

The best and easiest way is to create ring group 123 with the same destinations that ring group 1 has. Another option Is to create ext 123 and enable call forwarding on it to ring group 123

@ou812, thank you for the excellent suggestion. I plan to develop one, though it will not be available until approximately 2–3 weeks from now. In the meantime, if you would like a brief demonstration via Zoom to address any questions you might have, please feel free to send me a private message.

Sounds like you are building an app. I've never done it, but from the perspective of using apps, I know that the push server is always registered even when the app is closed, and as far as FreeSwitch is concerned, it thinks the extension is online. Your push server then needs to wake up the app...

I think you misunderstood me. FS PBX ensures complete separation of domains and tenants without relying on poorly formatted usernames. Additionally, we offer a multi-site admin user group for resellers that allows administrators to select which domains are visible to resellers and switch between...

In FS PBX, the domain is not required for variable configuration since everything is initialized based on the user's actual email and the corresponding domain. This design simplifies maintenance for both users and administrators, and it makes it easier for users to reset their passwords and...