We have had 2 instances on our deployments when the Numbering Plan has broken.
The following actions have occured which seem to trigger this, rename a single route filter and then broke all numbering and performing a restoration.
What happens is route filters do appear to be matched eg dial a mobile 0.04 (then bombs out as this will be the match). When bombing out added an explicit route pattern and worked ok.
The only way we have been able to fix this was to remove the route patterns, route filters, uninstall numbering plan, restart server, re-install numbering plan (perform this on both call managers).
Would like to know if any one has encountered this issue?