This is the first time I've seen it, but it appears to allow you to specify Calling Party transformation at the Route List level. Previously, these transformation could only be applied at the Route Pattern level or the gateway level. The problem with modifications at the Route Pattern level is that there may be (and should be) multiple gateways configured for that Route Pattern (for redundancy) and each gateway may need different Calling Party transformations; Some providers will reject calls if the CLID is not a DID associated with the transport trunk. Of course, the same thing could be done with translation profiles on the gateway, at least with Cisco IOS based gateways, but this provides a centralized method of handling these.
For example, my primary gateway has a trunk with associated DID of 952-555-2000 through 952-555-2099. My backup gateway has a trunk with DID in the range of 651-555-8000 through 651-555-8099. My extension is 2020 and my external mask is 952-555-XXXX. Therefore, normally, my outbound calls go out my primary gateway with a CLID or 952-555-2020. Say, however, that my primary T-1 goes down. The Route Pattern doesn't know that and still routes outbound calls to the Route List. The Route List gets a 'call rejested' message from the primary Route Group and so sends the call to the backup Route Group. However, it sends it with the 952-555-2020. My provider will reject the call if I try to send that CLID over that trunk. However, I have a Calling Party Translation Pattern on that Route Group that translates that Calling Number to 651-555-8000, so the call can go through.
