When an Internet service provider (ISP) in one geographical location provides service to two networks in different geographical locations, a three-zone configuration might be necessary.
|
Before You Begin |
|---|
|
For background information, read Understanding the MGCP ALG. |
In this example, (see Figure 127) an ISP located on the American west coast provides MGCP service to customers in separate networks in Asia and San Francisco. Asia customers are in the asia_3 zone and supported by the asia_gw gateway; San Francisco customers are in the sf_2 zone and supported by the sf_gw gateway; and the west_ca,call agent is in the DMZ. The gateways and the call agent are listed in Table 82, showing the corrsponding IP address, interface, and zone.
Table 82: Three-Zone ISP-Host Service
|
sf_gw |
2.2.2.201 |
ge-0/0/0 |
sf_2 |
|
asia-gw |
3.3.3.110 |
ge-0/0/1 |
asia_3 |
|
west_ca |
10.1.1.101 |
ge-0/0/2 |
DMZ |
After creating zones and setting addresses for the gateways and the call agent, you associate the zones and addresses to interfaces, and then configure NAT (ge-0/0/1.0) and policies.
Figure 127: Three-Zone ISP-Hosted Service
To configure a three-zone ISP-hosted service using source and static NAT, use either the J-Web or CLI configuration editor.
This topic covers: