Search results

Postmarkapp.com

Before the answer command in the dialplan try to set or export (i forgot which one does the trick) absolute_codec_string=PCMU assuming the SIP call to the outside is using G711U

I think 4 GB of ram is the minimum requirement, otherwise it will work fine on AWS. No, it is not ram intensive while running normally; it’s just the initial build process that demands the ram

This issue has existed for years already. I found myself having to make the changes from the database manually. FS PBX, an alternative to what you are using today, solves a lot of these bugs including this one.

If call forward is being set with the system feature code and NOT through the endpoint itself, you can potentially check for the SIP diversion header as a condition

To add to that, 6 more pages were just converted in the last week. We manage over 3000 endpoints with FS PBX and we will never look back. It's probably the only open source front end that is literally ready to go once you install it and plug in the core information. It is also being developed by...

Freeswitch can crash and yet still respond to the SIP tcp port that you’re monitoring in AWS. How are you handling such instances? Have you found a way for route 53 to specifically check for SIP options?

with an SBC

We service >3000 endpoints in production and moved all those PBXs to FS PBX

nothing wrong with going in that direction either. Maybe just have a primary and failover server. All traffic routes through the primary. Failover is only when there’s a problem or scheduled maintenance and you make dns change so that no one will ever need to know about the second login

How about two central DB servers that are replicated against each other in two separate geographic regions, and then spin up as many PBX servers as you desire, that will either connect to centralized DB server A or centralized DB server B?

That’s exactly what I did. May not be the most perfect solution but it does the job. The alternative that comes to mind is to create a lua script for each outbound call. The lua script runs a Postgres query against your configured DIDs. If there’s a match, then no diversion header is set (and...

What I do is I set a tag on all inbound calls. When placing an outbound call, if the tag condition is met, I automatically add diversion header, as this assumes that the call is being forwarded. Any call without a tag means that the outbound CID was set from the system and can safely be passed...

Something else to consider. recent FCC mandate requires VoIP resellers to do their own stir shaken. You cant legally rely on your carrier to do it for you if the phone bill is coming from your own company.

If you are experiencing memory leaks then you should look into your programming. I manage multiple servers that handle 1000 endpoints each and I have not rebooted in several months

While this patch helped resolve the issue at 00:00 on 1/1, there is still another issue that someone else brought up. Long story short, this issue can still be reproduced after the new year when freeswitch gets restarted. So I am recommending to revert back to original code while the developers...

No, it wouldnt make sense to have to pause replication every time you wanted to back up. That wouldnt be ideal practice. Proxmox images are for disaster recoveries or scheduled maintenances That said, if you are performing scheduled maintenance and need to move things around, that’s one...

Yes. Disable PG replication on both nodes. Take your snapshot. Restore. Re enable replication. The command, off my head, is: alter subscription <subscription name> disable;

In theory it should although I have not tested that. If I take a snapshot of my instance right now without suspending PG replication, and in an hour from now I restore that snapshot, in the last 60 minutes there would have been, at minimum, CDR transactions that took place. If the database...

Restores are straightforward If you use DB replication you just need to get that re-established with the new IPs and/or with the most up to date database information