You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

In this section:

Use this scenario to establish minimal configuration to facilitate test call across two sub-networks.

Background Information and Dependencies

The initial configuration is performed with the following background information:

  • System has been assembled and software installed at the factory.
  • System is cabled together (HA) and into the customer's network.

The 

Unable to show "metadata-from": No such page "_space_variables"
 defines the default instances for most profile objects.

The initial installation specifies the values for the following required entities:

  • Administrator account
  • Default system name
  • Two physical servers, or computing elements (CEs), with default names
  • Hardware link interfaces (ports) per server, with default names (pkt0 - pkt3)
  • Redundancy configuration
  • Management and HA interfaces IP address, net masks
  • Management Interfaces default Routes

Workflow

The following procedure assumes that the management IP interfaces have already been configured as part of the

Unable to show "metadata-from": No such page "_space_variables"
setup.

  1. Login to CLI and Enter configuration mode.
  2. Define signaling/media IP interfaces.
    1. Set the IP Address and Network prefix.
    2. Associate it with the physical ethernet port or VLAN on that port.
  3. Set up signaling/media IP routing
    1. Add Static IP Routes for peers on the trusted network.
    2. Add Static IP Routes for peers on the untrusted network.
  4. Define the allowed media parameters.
    1. Set the Codec type in the Packet Service Profile (PSP).
  5. Create the core network zone.
    1. Create the Zone “default.core”.
    2. Assign the SIP signaling port address.
    3. Define SIP Trunk Groups for peers.
  6. Create the untrusted network zone.
    1. Create the Zone “default.untrusted”.
    2. Assign the SIP signaling port address.
    3. Define SIP Trunk Groups for peers.
  7. Create core network IP peers.
  8. Create untrusted network IP peers (static, not registering, peers).
  9. Create call routes to network IP peers.
    1. Create routing label “to_core”.
    2. Create Standard Route “599625” using routing label “to_core”.
  10. Create call routes to outside IP peers.
    1. Create routing label “to_untrusted”.
    2. Create Standard Route “599626” using routing label “to_untrusted”.

  • No labels