Inbound Rules search seems a bit buggy

[mpruett]

I didn't see a bug report section so I'm posting here:

I have been doing a lot of work on cleaning up our rules recently and noticed that the search function in Inbound Rules will often return result that do not contain the thing I searched for. I imagine this is easy for anyone to recreate. As an example if I search for 299 I get two results, one is a valid match that matches on both the name and extension which contain 299. However the other result's name is "349 - End Call" with the rule going to end call. There is no reference to 299 in this rule. Especially when dealing with hundreds of rules this is really annoying, and I had to resort to naming them all so that I could pick them out of the sometimes long list of bogus results. 299 was just one I randomly entered just now, but these false results are common. If you want any further information let me know.

Thanks.

 

[Leonardo Rebelo]

i'm not really sure what you mean.

 

[JosIPVG]

He gets false positives when looking up a DiD in inbound rules , but i have tried this on multiple systems and havent been able to replicate it yet.

"349 - End Call" does the number belonging to this inbound rule have 299 somewhere in it? so not just looking at the name and its destination.

 

[mpruett]

Attached are images of the rule. This trunk is a t1 and the 3cx system does not get the full phone number on the trunk. So the DIDs are all in the form of *xxx.