In this section:

Scenario

Configuring a peering relationship across Carrier-A and Carrier- B and routing calls between them.

Background Information

  • 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/SipServer-combination-based routing models.
  • The customers' networks are represented by specific points of contact, i.e. by SipServers, rather than a set of machines (SipTrunkGroup).
  • 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.

Workflow

  1. Set "CLI context" to default Address Context default.
    NOTE:  Default is pre-created, but must set command-line context to it in order to create sub-objects within it.
  2. 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.
  3. Create a SipTrunkGroup with name "GCTrunkGroupA" within Zone "Carrier-A". Associate the TrunkGroup with the IP address ranges from Carrier-A.
  4. Create a SipServer with name "GCPeer" within Zone "Carrier-A".
    Set the IP Address of the SipServer as 1.1.1.2.
  5. 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.
  6. Create a SipTrunkGroup with name "GCTrunkGroupB" within Zone "Carrier-B". Associate the TrunkGroup with the IP address ranges from Carrier-B.
  7. Create a SipServer with name "Carrier-B Peer" within Zone "Carrier-B". Set the IP Address of the SipServer: 3.3.3.2.
  8. Create Routes to route calls from Trunk Group “GCTrunkGroupA” to egress Trunk Group “GCTrunkGroupB” and Peer “CarrierBPeer”
  9. 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.

  • No labels