This is a great way to handle security withing the PBX and allow freatures on an Extenshion basis. COR (Class of Restirction) could be handle like this.
1. Set up a Web page that would all for building of COR pages
This would be an example of a COR that allows Transfering, Confrencing and outbound dialing.
COR 22
1.Transfer
2.Confrence
3.Local (555-XXXX)
4.Longdistance (1-704-XXX-XXXX)
So basicly you want blank COR pages that can be populated by an admin with features. The admin would name the COR (22 or whatever number from 01 to 99 that they wanted) and then put the features that COR 22 can do. Then on the Trunk and extenshion pages we would need a field call COR and if the admin wanted a single or multiple extenshions to have these freatures then they would just populate the COR on the extenshion page with 22. This also works for trunks if you do not want to allow a trunk to be used for Transfering or Confrenceing (Like a call comes in to the PBX and is transfered to a personal cell Phone) you would give the trunk a COR that does not have the transfer freatures. This would stop hackers from using a trunk for transfering calls of net.
Its a very powerful tool used for security by TDM PBX Admins to stop abuse and would take care of at least 4 other freature request I have seen regarding spacific extenshion being able to access long distance trunks. This is really hard for me to explain using email but I would be happy to have a call or chat session with a developer to elaborat if needed.
