Allocating a SIP Network Access Point (NAP)

This article applies to: Product Version
SBC 3.0, 3.1

You must allocate a SIP NAP for your system.

To create a new NAP

1-Click NAPs in the navigation panel ===

NAP NavigationMenu.png

2-Click Create New NAP ===

Create New NAP SIP.png

3-Create the new NAP ===

  • Enter a name for the NAP
  • Click Create

Create New NAP SIP1.png

4-Verify that the NAP was successfully created message appears ===

Create New NAP SIP2.png

Associate a SIP transport server with the new NAP

The SIP transport server will determine the local IP Address and port from which this NAP will be communicating with remote SIP devices.
Note: It is not recommended to use multiple SIP transport servers in one NAP, because NAP availability may be inconsistent if one of the transport servers is down. For redundancy, it's recommended to create two NAPs and create redundant routes that point to each NAP (using weighted load sharing, or priority routing, as required).

1-Select a SIP Transport Server from the Available list

2-Click "<<" to associate the SIP Transport Server with the NAP

Create New NAP SIP3.png

3-Enter proxy address

Create New NAP SIP4.png

Configure the access control list (optional)

A NAP with a specific proxy address does not need the Access Control List (ACL) to be explicitly configured, as the NAP will automatically accept incoming packets from the proxy IP/Port.<br.> It is still possible to configure IP address ranges in the ACL, to accept incoming calls from IP addresses other than the proxy.

Create New NAP SIP5 ACL.png

Associate port ranges with the new NAP

Port ranges will determine IP addresses and ports that will be used for RTP packets with calls using this NAP.
Toolpack will automatically choose non-conflicting ports from these ranges to each call.

1-Select a port range from the Available list

2-Click "<<" to associate the Port range with the NAP

Note: The port range does not have to be on the same IP Interface than the SIP transport server.
Note: Multiple port ranges on different IP interfaces can be used for load-sharing or redundancy. Each call will be assigned a port from one of the ranges in a "load-sharing" manner.

Create New NAP SIP5.png

Associate SIP Domains with the new NAP (optional)

Associating a SIP domain to a NAP will allow SIP users to register to this domain from this NAP. Users trying to register from a NAP that is not associated to the SIP Domain will be refused.

1-Select a sip domain from the Available list

2-Click "<<" to associate the SIP Domain with the NAP

Create New NAP SIP7.png

Configure settings for the following parameter groups as required (optional)

  • Registration Parameters
  • Authentication Parameters
  • Network Address Translation
  • SIP-I Parameters
  • Advanced Parameters
  • Click Save

Create New NAP SIP6.png

Since 3.0.103 you have the option to disable a NAP. A disabled NAP will refuse incoming SIP calls, and will not be used for outgoing calls.

Disabling NAP.png

How to Create/Update a NAP with Restful API

You can find how to create/modify a NAP with Restful API in the following link:

Creating/Updating a NAP with Restful API