Inbound rules disapearing

Status
Not open for further replies.

kakashi

Forum User
Basic Certified
Joined
Jun 29, 2020
Messages
36
Reaction score
2
We ran the update to the latest version 3cx v16 the past weekend. Since then, we've had multiple inbound rules disappear twice. Has anyone else seen this behavior or have any idea what might be causing it? Today it was fine in the morning, then midday, they were gone.
 
Any info on if this will be fixed in a hotfix? This is getting very irritating, everyday one or multiple of my inbound rules are either disappearing or completely changing their routing ever since upgrading to 16.0.641.
 
I agree. This is becoming a big problem. Every change done to a system extension that has a DID, the inbound rule get deleted for some reason. I have to be recreating the Inbound Rules after every change.
 
  • Like
Reactions: kakashi
Agreed, it's quite a business critical issue.
 
3CX support replied to my ticket. They are aware of that situation. They said that they will be releasing an update for that, but no dates for release as of yet.
 
  • Like
Reactions: jmitch11 and VoIPQZ
I have a failover SIP Trunk. Both from same provider, different IP. So I basically replicate whatever rule from one trunk to the other. I noticed that too. Seems like whenever I place a change to the extension or any other system number, one of the DIDs being routed to it gets deleted.

I have the same thing and am experiencing the same issues, and my provider when routing calls to the PBx uses one of these two IPs at random to send the call in. So the calls that are sent in via the trunk with the removed inbound rule ends up going to the default route in 3CX, which does not work well at all for most of my customers.
 
  • Like
Reactions: sfernandes
Thank you all for your feedback, issue is under investigation
 
  • Like
Reactions: sfernandes
Response from 3CX support this morning that is helpful for the time being-


"This is a known issue with the PBX which persists on the next version as well.
For the time being, the way to assign the DIDs to the extension and not have the PBX delete one of the inbound rules is the following:
  1. Go into the extension and delete the assigned DIDs
  2. Click OK to confirm
  3. Go back into the extension and assign both DIDs at the same time
This should solve the issue you are facing."
 
  • Like
Reactions: kakashi
Response from 3CX support this morning that is helpful for the time being-


"This is a known issue with the PBX which persists on the next version as well.
For the time being, the way to assign the DIDs to the extension and not have the PBX delete one of the inbound rules is the following:
  1. Go into the extension and delete the assigned DIDs
  2. Click OK to confirm
  3. Go back into the extension and assign both DIDs at the same time
This should solve the issue you are facing."

Unfortunately, this also deletes the name for the rules or any scheduling that's been set up for the rules. Good to know though. I may try this with a couple of queues that don't have 200 different rules going to them. Thank you!
 
  • Like
Reactions: sfernandes
Unfortunately, this also deletes the name for the rules or any scheduling that's been set up for the rules. Good to know though. I may try this with a couple of queues that don't have 200 different rules going to them. Thank you!


Oof, I did not think about that.

I have not confirmed this, but it appears that the inbound rules disappear after the extension, ring group, queue, etc... is modified. For instance my inbound rules in the test bed for this did not disappear until I went into the extension where the DIDs were assigned and then pressed ok. If I pressed cancel the inbound rules were not affected. This would make sense as to why I have not heard from a majority of my customers having similar problems.
 
Is there any timeline on when this may be addressed? We own upwards of 2000 numbers across multiple failover trunks and multiple sites and having to go in and re-add the DID's to the extensions anytime you need to make a change to an extension is really starting to get old fast. Not to mention if one of our techs forgets they need to do this and the user starts complaining they're not getting calls or their number isn't working, this can seriously impact the business. This is the type of bug that makes me consider a replacement phone system.
 
  • Like
Reactions: Plains_JosephW
Its a browser issue. Happens to me with Firefox..Also the list of phones is empty.. Works with Chrome or Edge browsers..
 
So, there doesn't seem to be any timeline on a fix for this issue. As previously stated by other posters, its getting real old checking every hour to see if any rules have disappeared, and when they do disappear having to to press "import" and do a re-import of all the rules.

As a temporary workaround, is there a way to automate this re-import of the rules via a script or similar so it just re-imports every hour? Any help would sincerely be appreciated.
 
  • Like
Reactions: kakashi
As a 3CX partner and community follower. We support this point. It is very critical and a fix needs to be implemented now.

Just adding a simple employee means we need to re-do the inbound rules.
 
bump

would love an official reply about timelines from 3cx
 
My client is not happy. They have a setup of around 2500 extensions. This bug needs to be rectified asap.
 
@JohnS_3CX is there any update you can provide on a timeline for a fix?
 
Unfortunately no, I would say Update 7 now provisionally.

As a temporary fix you may be able to work around the problem by deleting all the rules and recreating them manually (no import/export) which should ensure that they are mapped correctly, but if you have a very large number of rules I understand this may not be an easy task.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,990
Messages
590,164
Members
164,927
Latest member
tohoken1