Bug in inbound rules overview?

[SECOIT GmbH]

Seems like there is a bug in the inbound rules overview:

1. I have a set of extensions and inbound DID rules
2. An employee leaves the company and another one takes over the position. I rename the extension.
3. Going on the inbound rules the DID rule for this employee still shows the old name instead of the renamed one.
4. BUT: Opening the DID rule it shows the correct name

Can anyone confirm this?

 

[diamond9]

I have just tested this on my system, this does not occur, it immediately changes the name in inbound rules without clicking into the rule.
Im presuming your on the latest update etc?

 

[SECOIT GmbH]

Yes, I am on latest release.
Thank you for checking on your end! Strange that it works on your end. I just tried with Chrome and Firefox. Both same issue.
Even when clearing the browser cache it doesn't make a difference. Still shows the old name in the list.

On thing I'm making a bit off the rules: I don't use the "First Name" field. I only use "Last Name" and there I enter the full name in the form of "[Last Name] [First Name]". This is because otherwise 3CX keeps cutting the last name with longer first names on some phones and also some lists sort by first name then instead of last name.
So in Germany the last name is more important because a lot people share the same first name where in some asian countries for example a big part of the population share the same last name.

Maybe that issue is related to not using "First Name" field at all. I'll check.

 

[diamond9]

If that is the case and its because of the first name, you could just enter an initial to keep it working.

 

[JohnS_3CX]

Hi @SECOIT GmbH

It is best to completely sanitize the extension if an employee leaves for security and privacy.

Delete the old one, and create a new extension with the same number.

Add it to the correct groups and give it the rights you wish it to have.

As for the name bug you mentioned we will check to see if it is possible to replicate.

 

[Rhys Haskell]

I have the same issue however the calls do route correctly, so it doesn't cause too much of an issue.