If you have a premium license it is easier to use the database queries.
In your script you can get the calling number with the get call contact info step and then obtain the prefix with a string method. After that you use the database steps to build your query with the prefix and retrieve the information you need from your database (I guess that would be the hunt group extension) and send the call to that group.
If you don't have a premium license, then you would need to write and XML document with all the possible prefixes and hunt groups numbers, and take a look at it from the script.
I have Premium licenses. But I'm worried about the big size of the database, because in each call the system will need to check the calling number with thousands of database entries. Do you know if there is any limitation, timeouts, ... that can provoke a disfunction?
I think if you build your query like "select from where = <$callingPrefix>;", there is no need to retrieve the whole thousands of entries of one DB table, which is different from doing "select * from ;" there you are retrieving all the information within that DB table. So I think you don't need to worry about (someone else correct me if I'm wrong with that). Remember to use the release step everytime you finish getting the table data (this to close a SQL query and release the allocated resources used there).
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...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...
You have reached the Cisco Logistics Support Center.. To Check Status of your RMA, visit Product Returns & Replacements (RMA).
Need help? Contact us by Phone or Email.
Phone: 1800 553 2447 Option 4