My company has started working with a VoIP carrier to bring calls from our\nvarious regions into our centralized call center. Here's today's problem:\n\nThe incoming DNIS is 10 digits. The call center software only understands 7\ndigits. That was peachy when it was operating in one geographical area but\nnow if you just drop the area-code (US) then there will be overlap as those\n7 digits are no longer unique. Ick. The preferred solution is to gix the\ncall center software and we are working with our vendor on that. However. In\nthe interim I want to create a big map that will translate the incoming DNIS\nso that the number that reaches the call center software _IS_ unique:\n\n2025551212 -> 3100000\n2125551212 -> 3100001\n3125551212 -> 3100001\netc...\n\nSeemed like a fairly straightforward concept. So I jump onto my trusky cisco\nrouter (2651XM BTW) and notice that I can have like 2 billion translation\ntables but each table can only have 11 rules. This seems a bit odd and seems\ndesigned to make my life difficult as I just want one big table with a few\nhundred rules in it. (Can you even apply more than one rule to an\ninterface?)\n\nIs there a better way to do direct mapping (like the above)? I have a couple\nhundred numbers that need mapping and there isn't any simple transform that\ncan be applied that will guarentee a unique number (that I've thought of).\n\nThoughts?