Search results

Have you removed the old routes? Also pastebin a log from fs_cli, you should be able to see it evaluating the dialplan

So, if the order is 21 for the extension, it is probably ignored. You don't want a dialplan for the extension, you want an outbound route and modify the order of your outbound route so that the specific extension route comes before the generic outbound routes. You may also want to rename the...

None of that is relevant, post what you have in each individual outbound route

It will be working as expected, you have probably got a mistake in there somewhere hence the request for the dialplan setup.

Just as a PS to this and where it really helped recently in a real situation: I always use different datacenters/providers for the primary and secondary. We had a recent issue where routing must have gotten bad between our primary and some of our clients, others were just fine. The way I have...

You'll also have issues with things like conferencing and queueing. Load balancing just does not work well at all unless you have a very customised setup. This is probably a question for the dsip router guys, eg is it even meant to be able to load balance, I doubt it very much. Certainly, in a 2...

If you can start by posting us details of the outbound routes someone may be able to help.

Have you added anything to the access control list other than what you have been told to? Also, have you added any dialplans that catch more than they should?

See this post: https://www.pbxforums.com/threads/intalling-on-an-rpi4.8505/#post-34410

There was a discussion on this in the forums recently, I managed to successfully install on a Pi and posted details here. I meant to submit some proper pull requests but haven't had the time yet.

I'm not sure about the official position on mysql support but I believe there are some functions that use postgres and have no mysql equivalent. Postgres is also easy to replicate to give you high availability.

I use a heavily modified version of pyfreebilling. Also, cgrates should always be considered, its just an engine and would need much configuration. For me the number one priority is stopping fraudulent calling. Most of the other, I believe ASTPP included, rate the call at the END. This means if...

Can you post your updated version, others may find this useful?

I know we have a few people who have replicated installations for failover etc. Has anyone tried using an alternative DB. I know I have seen cockroach mentioned a few times but another alternative that has come up that looks quite good is YugabyteDB, anyone taken a look?

Yep, I think you are right, I definitely had the 7940s and later, 7960s, I never had any of the ones ending with a 2.

I've just found this from 2012, it would definitely be for fusionpbx though: image_version: P0S3-8-12-00 # Line 1 Setup line1_name: "603" line1_authname: "603" line1_shortname: "DMM" line1_password: "U.YokaH.21" line1_displayname: "603"; proxy1_address: pbx05.mydomain.com...

I will probably have a conf file somewhere that I used to use, I'll see if I can dig one out.

Is all done with tftp and config files, I used these for years, they are good phones but terrible to work with on any thing other than call manager. Throw them away and get a proper ip phone.

I installed it on this by the way, a rackmount blade module with a CM5:

So download the installer: wget -O - https://raw.githubusercontent.com/fusionpbx/fusionpbx-install.sh/master/debian/pre-install.sh | sh; Then replace these two files in the /usr/src/fusionpbx-install.sh/debian/resources directory Then edit...