Let me see if I understand the problem:
* You need to differentiate between mobile calls and land line calls, presumably so you can route them via different service providers/trunks, block them, bill them differently, etc. Previously you used Route Patterns for this.
* Prior to Aug 3, outbound calls to mobiles are prefixed with 044 or 045, and outbound calls to land lines were prefixed with 01. This makes them easy to differentiate.
* After Aug 3, outbound calls to mobile and land lines will both have the same basic format, i.e. 10 digits starting with the area code. This makes them difficult to differentiate.
* Some kind of government provided database will be made available that identifies all mobile phone numbers/ranges
If I'm mostly right, some thoughts/questions:
* How many entries are in this database? If the number is in the hundreds to a few thousands, it may be possible to just create/maintain a bunch of translation/route patterns - which could be automated using the CUCM AXL SOAP API. My understanding is that the max number of patterns is constrained by the CUCM performance profile based on the underlying server hardware, and that you can use the CUCM sizing tools to validate a particular configuration (total devices, lines, patterns, etc.)
* If the number is too large to use patterns, then you need to consider coding an application that will examine every outbound call, do a dynamic database lookup to check if its mobile, then route the call to the appropriate destination. There are two APIs that might be suitable here: CURRI and TAPI / JTAPI (CURRI is probably the more approachable one.)