In this section:
During residential deployment, the addresses of the peers are not known in prior. The SIP endpoints make themselves known to the SBC Core through SIP registration message which is flowing through the SBC. This type of deployment always has one or more SIP registrars residing within the core IP network of the SBC's owner.
The Residential Access contains large number of end-points hence, the SIP end-point need to be provisioned for different level of services.
Asterisk indicates the fields are mandatory.
Prerequisite
You can use the default Address Context or create a new Address Context in the Navigator.
Prerequisites for the workflow SIP Residential Access are:
- Address context
- IP Interface group
- IP Interface
Workflow
This section provides a high-level understanding of SIP Residential Access Provisioning.
SIP Residential Access Provisioning Flow
The following figure shows the provisioning flow of the SIP Residential Access
Step 1: Set up the Zone
Perform the following tasks to set up the Zone.
- In Workflow, click SIP Residential Access > Zone.
- In the Address Context drop-down list, select the address context.
- Select Zone from the drop-down list.
- Click Next .
- To create a new Zone, click Create New Zone next to the Zone drop-down box, and enter the following details:
- Zone Name
- DNS Group
- Zone Id
- Click Save.
For more information on creating Zone, refer to System Provisioning - Zone.
Step 2: Add a SIP Trunk Group
Perform the following procedure to add the SIP Trunk Group.
- Enter the SIP Trunk Group Name.
- Enter the details of the following:
- Policy
- Packet Outage
- Call Reservation
- CAC
- Services
- Media
- Call Routing
- Ingress IP Prefix
Click Next .
The following dialog appears:- Click Yes to add more SIP Trunk Group and click No to proceed.
Step 3: Finish and Save
Click Finish and Save. The result of this action is displayed.
Click OK to exit.