Local Route Groups

Local Route Groups(LRG) feature reduce the complexity of the numbering plan when you have a large number of locations.

Consider the following scenario.

In the picture, we have Callmanager at HQ and phone from each branch register to Callmanager.
 
Each branch has their own PSTN gateway, so in Route Pattern configuration we need 5 Route Patterns with 5 Partitions and phones from each branch have CSS to access their own PT and then to their own gateway.

With Local Route Group we can simplify this route plan. Consider the following picture

As you can see, each branch has their own Device Pool associated with their own LRG and then their own gateway.

With this configuration, we achieve the same result with only 1 Route Pattern.

When a phone initiate a call to outside and then match Route Pattern --> Route List

The Route List contain special route group that is named Standard Local Route Group.

At this point system will check the phone's Device Pool and see which Route Group associated.

Then call will be sent out to gateway associated to that Route Group.

Detail Configuration,

Step1. Create 5 Route Groups and associate gateways to Route Groups.

Step2. Create 5 Device Pools and associate Local Route Group in Device Pool with Route Group created in Step1.

Step3. Create Route List and associate Standard Local Route Group to this Route List.

Step4. Create Route Pattern and associate Route List to this Route Pattern.

Step5. Associate each Device Pool to phones.

Step6. If call sending out to each local gateway require different CLID, we need to use Calling Party Transformation Patterns to manipulate Calling Number for each barnch.

For example BR1 with DID number 021267XXX and extension number 7XXX.

Step6.1 Create Calling Party Transformation Patterns (Partition is required)

Step6.2 Create CSS that can access Calling Party Transformation Patterns Partition in Step6.1 in this case CSS_BR1_CLID

Step6.3 Associate CSS_BR1_CLID to Calling Party Transformation CSS in Device Pool or Gateway.

If you associate CSS_BR1_CLID to Gateway make sure to uncheck Use Device Pool Calling Party Transformation CSS.