IMO there should not be any issue with adding both patterns. Remember you will route the 141 to PSTN or mobile network which will then hide the callerID. Therefore you should add both to satisfy the requirement.
The other thing which is good to know, is that PSTN or mobile networks are expecting a certain number of digits in the callerID. So, if you prefix that with say any 5digits - I have seen the number come up as unknown. This one method to achieve callerID masking by yourself instead of relying on public phone networks.
I am struggling to think of any way you could merge two route patterns into one. Anyway two are better than one ;)
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...