Not sure if this is a problem, but I noticed a couple of issues with the new "call_direction-outbound rule" that is now created for each new "outbound route"
1. Initially the Regex in the "call_direction-outbound rule" is the same as the Regex in the matching "outbound route". However, if I make changes to the Regex in the "outbound route" (which happens), those changes are not passed down to the "call_direction-outbound rule" i.e. don't match anymore.
2. If I delete an "outbound route" (for whatever reason) the matching "call_direction-outbound rule" is not deleted and stays there forever. Isn't that a problem?
3. If I delete the "call_direction-outbound rule" and keep the "outbound route" there is no warning message.
If this new "call_direction-outbound" rule is really required, shouldn't there be safeguards or warnings to ensure it always matches with the corresponding outbound rule? What happens if a system has many mismatched and leftover "call_direction-outbound" rules? Just wondering.
1. Initially the Regex in the "call_direction-outbound rule" is the same as the Regex in the matching "outbound route". However, if I make changes to the Regex in the "outbound route" (which happens), those changes are not passed down to the "call_direction-outbound rule" i.e. don't match anymore.
2. If I delete an "outbound route" (for whatever reason) the matching "call_direction-outbound rule" is not deleted and stays there forever. Isn't that a problem?
3. If I delete the "call_direction-outbound rule" and keep the "outbound route" there is no warning message.
If this new "call_direction-outbound" rule is really required, shouldn't there be safeguards or warnings to ensure it always matches with the corresponding outbound rule? What happens if a system has many mismatched and leftover "call_direction-outbound" rules? Just wondering.