I understand that In order to use a DID. You have to set up the DID in the Origination Rates Table.

I think the following changes would vastly improve the issues with Origination rates not found when dealing with DIDs.

1. When a DID is assigned to a customer, make sure the system automatically creates the DID code in the origination rates table with the rate group of the customer that owns the DID.

2. If you change the rate group on the customer account, automatically update the Origination Rates of all the customers DID to the new rate group.

3. On the DID's section of a customer account - If the DID is not in the Origination Rates table at all or if there is not a record in the Origination Rates Table with the did AND the rate group of the customer - Show an Error Message on this screen, and maybe an auto fix button that will generate the rate.

4. Optimized Call Routing - Also since ASTPP knows where the DID lives. It would be nice if you select force trunk option, the system would present a list of all the rate groups and allow you to select the rate groups you want an record inserted into with the force trunk. This would then make it so the system would not utilize a provider trunk to call out, but would keep the call on-net and there by reducing any costs that would be incurred by dialing out to the pstn and back in.