Page 98 of 258 Bandwidth Management

Differences when every branch office HLOC is shared with the main office

Table 7 shows the configuration when the branch office HLOC is shared with the main office.

Table 7

Provisioning details for this case

Region

Provisioning detail

1Provisioning on the main office requires parsing to only “normal” LOC identification and HLOC deletion.

1LOC values that are on branch offices may be provisioned as extended LOCs (> 3 digit codes).

1The DMI for the branch office “LOC” inserts a gateway routing prefix in front of the number.

2,3

Similar configuration, as above, applies to regions 2 and 3.

Call between two branch offices associated with the same main office

The following scenarios describe calls between two branch offices that belong to the same main office. the different scenarios described below vary vary in the manner in which the HLOC is architected; branch offices have same HLOC as the main office, branch offices have a different HLOC than the main office and so on.

Every branch office HLOC is shared with the main office

In the following example, the HLOC of all the branch offices and the HLOC of the main office are all the same. See Figure 21 on page 99.

553-3001-207 Standard 2.00 January 2006

Page 98
Image 98
Nortel Networks Remote Gateway 50 manual Every branch office Hloc is shared with the main office