...
...
...
...
Back to Table of Contents
Back to SBC Network Deployment Scenarios
Back to H.323 Deployment Scenarios
Scenario
Configuring H.323 peering across Carrier-A and Carrier- B, and routing calls between the carriers.
- The system is installed in a service-provider's network interconnecting two of its customers.
- The system exposes only the Trunk Group based routing and the Trunk Group/H.323 Server combination based routing models.
- The customers' networks are represented by specific points of contact, i.e. by H.323 Servers, rather than a set of machines (h323TrunkGroup).
- The requirements specified in the section "Background Information and Dependencies" under Minimal Out-Of-The-Box Configuration are met.
- Ports and IP Interface Groups have been configured as described in NNI: Complex route selection.
Configuration Steps
- Set "CLI context" to default Address Context.
Default is pre-created, but must set command-line context to it in order to create sub-objects within it. - Create a Zone with name "Carrier-A". This Zone can use LIFGroup1 by default as this is the only IP InterfaceGroup defined in this Address Context.
- Create a H.323 with name "GCTrunkGroupA" within Zone "Carrier-A". Associate the TrunkGroup with the IP address ranges from Carrier-A.
- Create a H.323Server with name "GCPeer" within Zone "Carrier-A".
- Set the IP Address of the H.323Server as 1.1.1.2.
- Create a Zone with name "Carrier-B". This Zone can use LIFGroup1 by default as this is the only IP InterfaceGroup defined in this Address Context.
- Create a H.323 with name "GCTrunkGroupB" within Zone "Carrier-B". Associate the TrunkGroup with the IP address ranges from Carrier-B.
- Create a H.323Server with name "Carrier-B Peer" within Zone "Carrier-B". Set the IP Address of the H.323Server: 3.3.3.2.
- Create Routes to route calls from Trunk Group “GCTrunkGroupA” to egress Trunk Group “GCTrunkGroupB” and Peer “CarrierBPeer”.
- Create Routes to route calls from Trunk Group “GCTrunkGroupB” to egress Trunk Group “GCTrunkGroupA” and Peer “CarrierBPeer”.
The system will now route the traffic from Carrier-A to Carrier-B and vice-versa.
...