Search results

You guys have clearly not been sitting still. Will upgrade to 2.0 today. I also see the comments on the version upgrades not but I am lost on Dynamic routing. Dynamic routing as I know it, routes inbound calls based on the caller ID of the caller - if no match, it takes the normal route. That...

I think that was in reply to my other ticket :-) rather than this one. But thank you - will try that!

Something that has plagued us for years on FusionPBX, no matter the version and also on FSPBX is the fact that often, but not always, after a restart of either just FS or the whole server, there is no sound in the ringback even though it's a 183. Reloadxml without fail sorts that out and is easy...

Did an upgrade last night - even though github has 1.9.7 as the last update, I am now on 1.9.9. Didn't poke around yet but see things like Dynamic routing and ai agent. I assume that you are just running behind in updating github and docs and that I didn't accidentally end up on a version that...

Thanks for the alert! We still had an old, inherited, Fusion box (don't laugh, FS 1.6 still) running that was more or less forgotten about with a handful of customer. Have just hammered it shut and will move the few customers over asap. I think I got there in time.

they can still connect with tcp/udp

My understanding is that, unlike previously with just fail2ban, if wrong credentials are used while registering, but other devices are already registered from that public IP, it will only ban that extension but not the whole public IP address. If however there is nothing yet connected from that...

it won't hurt I'm sure, we just haven't had to at all. Then again, we run a handful of VMs per node max, so there are always plenty of resources available.

Use KVM - and if single node only set cpu = host although I am not sure if I have really noticed a difference. Other than that, I have never had to do anything specific and it runs without any issues.

I am not sure why in this particular instance it would be different with Fusion vs FSPBX, but certainly on our instances of Fusion we see all kinds of variations of this. SIP ALG definitely messes with this kind of thing and we tell all customers to disable that but depending on the...

Check if you have any of the NAT helper stuff enabled on the one and not the other? Then again, I just looked a customer who I know uses fanvils. Some phones show the LAN ip, others don't. Same location but different models and firmware versions............

Mine is all over the show, always has been though. Some customers show public and private, others show only public, again others will on some phones both, on other phones not. Sometimes it will be the same model phone with different results. Fanvils typically have never shown the private IP...

Yes - for some we do exactly that but for many others that won't work because of different requirements. Each customer is different of course and we try and keep it as simple as possible. We have some who use the feature codes, but call forwarding is seldom done on an extension level for most of...

Good call - and we actually used to do that - but typically customers don't read their emails either :-) and we stopped this. Maybe we just have very difficult and lazy ones. You reminded me of this though now and what would actually work better is to extract the email addresses of those who...

I agree with doing it ourselves to a large extent to avoid silly mistakes such as call forwarding loops. And indeed, once the initial setup is done, not much happens anymore. BUT - and this is the killer for us - Business hours should be done by customers. When a public holiday comes up...

We have played with the idea (and tested) of charging for this but have found it's the quickest way of losing a customer- they simply won't pay for it or pack up and go. It really should be charged for, I agree and maybe we will just build it into the price of the PBX but that's not easily done...

We often battle to get customers to do anything themselves. Of course one of the reasons for choosing FSPBX was an easy to understand customer interface. But we are finding so much resistance. "I don't have time to read a manual - just tell me what to do, or do it for me" is the refrain. There...

Maybe I have not understood BLFs for what they are. I have only ever understood them to show that someone is engaged, nor for any other purpose. A quick google shows me that it can also be used to show someone else's phone is ringing and you can then use it to pick up the call. But that aside -...

It does work fine without using call groups - but for bigger customers that is often not suitable. We don't do it via BLFs - users just dial *8 Customers often have multiple branches - let's use one as an example who have 17 restaurants. A call comes in to restaurant A, and at the same time...

We have the diversion header working on it, but it doesn't have the correct number listed in the header. Will play some more with this to see if we can make it work as it would be the ideal way of doing it. This diversion header requirement is a real pain but we don't have a choice - calls to...