Manish - you will need to use Logical partitioning feature of the CUCM. Refer to dial plan section in the below document for understanding:
Some countries such as India have Telecom regulations requiring an enterprise's voice infrastructure to use the local PSTN exclusively when connecting calls outside the enterprise. This requires that the voice system be partitioned logically into two systems: one for Closed User Group (CUG) communications within the enterprise, and a second one to access the local PSTN. A call from an enterprise user in location A to another enterprise user in location B could be made within the CUG system; however, a call from an enterprise user in location A to a PSTN destination, no matter the location, must be made through local access to the PSTN in location A.
Please rate all helpful posts
Hello Terry, I have read some threads about this topic, seeing you have some hands-on experience maybe you can share about this... Is it possible to have a single cluster to serve restricted countries like India, and in the same cluster serve countries without the same restrictions, like in Asia ? or I keep it simple and build 2 clusters, to make sure an enterprise parameter is global, and cannot configure as I would need the global parameter in for the India site versus the Asia site ?? Finally, did you dedicate a cluster for india only ?
to add to this. Personnally, I think building a second cluster to fullfil the local PSTN hop off requirement. Is not keeping it simple. In fact i thnk it makes your deployment worse in terms of admin overhead and points of failure. I would use partitions and CSS to fullfil the requirement. (like Terry already mentioned). With Standard Local Router Groups, this requirement is easy to fullfill. Countries that do not share that requirement, just use different route patterns, with TEHO for this, again, in combination with logical partitioning.