The objective is to create 1230.xml, calling number which matches the data inside the xml file will be directly transfer to ext 1230 queue. There will be multiple xml file for multiple extension number.
It seems the solution in my mind is not very scalable as it will be checking through multiple xml file before making routing decision.
Just to confirm I understand your request: You want to route the caller to a specific destination or CSQ based on their ANI?
If that is accurate, you will need to figure out a common way to store the ANI so you can match it in XML or SQL. This is somewhat easy within the U.S. as NANP is a fixed-length dial plan. Countries with variable-length dial plans make more challenging.
You can use XML (and a single file) by just having different elements for each ANI pattern and use XPath to get the appropriate child element(s) that explain the final destination to route the call to.
Likewise with SQL if you have premium: You can run a SQL query and get the result back.
If you are going to have hundreds, or more, of these ANI-based routing scenarios you will likely need to use SQL. CCX has to load the entire XML file into memory each time the script is called so this could become a problem if the file is overly large and/or a lot of concurrent executions occur.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...