Originally posted by RobertWC;32532
I would suggest a handler that keeps them all in one easy place. An IP table with a quick handler lookup would be the best. Write me back if you want details. As for number, it is the total characters you can store in a registry key which I think is 16,383 characters.
Thanks for the info Robert! We have a table already that has the DNIS, Skill, AppCode, Whisper msg, and priority. Today we have over 200 profiles and a whole lot of handlers. We are constantly moving or adding DNIS's around within the profiles.
I wanted to create a Routing Profile. I would add the Attendant Profile Name to the current table. I wanted a way to migrate the existing DNIS's to this Routing Profile without having to put the DNIS's in the Routing Profile. That way the only place we had to change any DNIS is in the Table instead of in the profile and the table. I used 0000000001-9999999999 in the profile but it errored in the publish that the numbers already existed. I thought the hierarchy was exact match, range and wildcards. If I could get that to work, as they were ready in the table, migrate the DNIS in existing profiles to this Routing Profile by removing the exact match DNIS. Eventually all calls would go to one profile, read the table and route to the correct profile in the handler. We would have only One place to keep up with the 1,268 DNIS's and the group keeping up with these could do it when they wanted and not have to involve publishing.
We are experiencing issuses with publishing so we have to do it once a week after hours. sorry for the wordy post...