AACC CLID routing issue

[schmitzfl]

I have AACC 6.2 on a CS1k. I've built out a CLID table to route calls to a specific App. Sort of like a "Platinum Customer" list. I built the original list (clid_esn) with a few cell numbers to test, all worked fine. After that I added about a 100 more numbers to this list to place it into production. To continue testing I added my cell number to this CLID variable but calls from my cell are not routing to the desired App. So now I don’t know if all of the numbers on this list are routing to the correct App. I can build a new test CLID list and add my cell to it and it routes correctly.
This global CLID variable is in the beginning of my Master App and looks like this;


WHERE CDN EQUALS

VALUE 9030: EXECUTE SCRIPT ESN_AUTO_ATTN_App
VALUE 9031: EXECUTE SCRIPT ESN_AGNT_App
VALUE 9032: EXECUTE SCRIPT ESN_AGNT_SVC_App
VALUE 9033: EXECUTE SCRIPT ESN_REVERT_App

DEFAULT: EXECUTE CLID_LOOK_UP

END WHERE

SECTION CLID_LOOK_UP

IF CLID = clid_esn
THEN
EXECUTE SCRIPT ESN_AUTO_ATTN_App
ELSE
EXECUTE CDN_ROUTING
END IF


The ESN_AUTO_ATTN_App is used for an Auto Attn that may route calls back to the Master Script to be sent to one of the other ESN Apps, this is why I have this small group of CDN's up front of the CLID check.

My question is, why wont any new additions to this large CLID table work?

 

[effort1584]

Variable sets are limited to 100 entries (version dependent, it used to be 60). Unfortunately the variable page will let you enter more than the allowed number. Take some out and build a second variable/script to process it.

 

[Supernn]

You could also try to have a HDX lookup.
This way you can crosscheck the valid CLID's with a database any size.

The HDX connection should be made on the AACC server and can connect to at least MS SQL and MySQL

 

[schmitzfl]

I was thinking it could be a size limit. Docs are limited at best,,, Thank you for your assistance!