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

Compare with Current View Page History

Version 1 Current »

Back to Table of Contents

Back to SBC Network Deployment Scenarios

Back to Service Provider Deployment Scenarios

Back to Access (UNI) Scenarios

In this section:

Scenario

 Establish configuration to support a large group of residential VoIP subscribers.

Background Information

  • Residential customers reachable through physical port “Port 3”.
  • IP addressing for residential customers does not overlap with any other customers or the core network.

Workflow

  1. Set "CLI context" to Address Context "default"
  2. Create IP Interface Group "default.Subscriber_Access"
  3. Create and configure IP Interface "default.Subscriber Access.LIF3" in "Subscriber Access". Set "LIF3" name/IP address/netmask/VLAN tag.
    1. Associate IP Interface "LIF3" with Port "Port3"
  4. Create a Zone with name "Portland".
  5. Create a Sip Signaling Port "default.Portland.Subscriber Signaling Port" for this Zone. Set "Subscriber Signaling Port" IP address.
    1. UDP, port 5060 is set as default; TLS is disabled by default.
    2. All subscribers in this region/context will direct traffic to this Sip Signaling Port IP address.
  6. Create a SIP Trunk Group with name "Subscribers" within Zone "Portland".
  7. For routing calls from each subscriber to the outside world, re-use the Routing Label created in the previous deployment scenario: "To Core Network".
No specific profile references are set in the SIP servers, so all are set to the Default Profiles.

  • No labels