There may be times you'd want to have a common feature code but send users to a different actual destination based on CallerID (Call P-A-G-E to do a page in YOUR zone, etc. - maybe not the best example but there might be hundreds of potential ways this could be used). While you can fudge this functionality using outbound routes and custom trunks, it would be a lot simpler if the Misc. Applications feature had an optional CallerID selection field, similar to Outbound Routes. I don't know if this makes sense from a programming standpoint, but if it's not too difficult it would be a good alternative to other, more cumbersome ways to do this.
While writing this, it occurred to me to try adding a / and caller ID number or pattern to a Misc. Application feature code and see if it works as you might expect, allowing only the extensions specified to use that particular Misc. Applications rule, and apparently it does. So, all that would be needed is to break the CallerID field out into a separate box, to be consistent with Outbound Routes, and to make it obvious that you can limit Misc. Applications to particular CallerID's. Also that Misc. Applications are processed in the order shown and that the order of Misc. Applications can be rearranged, if that's not already the case.
