Quote:
|
Originally Posted by martinyoung
You are correct, CORs can't be changed automatically for any reason. The only thing that can change automatically what happens to a route pattern using the time-of-day table that you associate with the partition route table.
|
... and THAT will not change the COR meaning that the use (or not) of Auth Codes would not be affected.
Quote:
|
Originally Posted by martinyoung
As an aside, I have seen many customers use partition route tables. And when you go to the table the only entry is for time-of-day table 1 which is set for default 7/24 availability. Plus they would have partition route table 1 routing calls to route pattern 5. They have complicated their programming for no purpose and you cannot explain that to them. :D
|
I hate partition routing tables. The only valid usage is if you have multiple groups that you need to point to different pipes ... such as multiple tenants ... otherwise (like you said) you simply add an additional layer of complexity that is completely unnecessary. We typically remove them from the software during upgrades unless the customer can produce a compelling argument that requires them.
regs,
.al.