Emergency Responder should not be needed for this. You can do this using the line/device CSS approach. The concept is documented in the UCM SRND; however, the idea is that calling privileges are placed on the line CSS while all call routing is performed on the device CSS. In essence the line CSS ends up being only a list of blocked route/translation patterns of what that DN is not allowed to dial. The phone is configured to route all calls appropriately to it's physical location (which can be dynamic if using device mobility). Since the line CSS takes precedence when a match is found in both, the user will be denied if their line CSS has the block present.
As a side note, if you do not have this already, I presume you have only a single CSS on the line or device. Moving to the line/device CSS can be a moderate undertaking. You may also want to evaluate the new E.164 dial plan design introduced in UCM 7.0. This builds upon the line/device CSS model but is implemented fundamentally different in UCM. This is also documented in the UCM SRND but does take a while to understand.
Lastly, there is a limitation with the line/device CSS that could be a minor nuisance: the calling privileges assigned to the line CSS are not aware of their location at any time. This means that if you prevent a user from dialing long distance, the line CSS has no way of updating to know what "long distance" is when they roam to another site and login using extension mobility. They would still be restricted to dialing local calls from the perspective of their home site even though those would now be long distance. If you are in the United States, Canada, or parts of the Caribbean this is mitigated by the NANP. This is because NANP is a fixed-length dial plan which allows you to place restrictions based upon the dial string length (i.e. local is seven digits, long distance is ten digits, international starts with 011, etc). If you are elsewhere in the world or if you want to use the E.164 dial plan design, you loose this predictability.
