Port Sharing for SIP Node

Efficient SIP node management with shared ports

The Port Sharing for SIP Nodes feature in anynode – The Software SBC allows multiple SIP nodes to use the same transport, making them accessible via a single port. The node selection is determined through a configurable whitelist in the SIP node object or the transmitted local SIP domain.

Configuration is straightforward with the Node, assistant ensuring no critical settings are overlooked. The wizard includes a SIP transport menu item, which prompts users to create a new SIP transport for future use by other nodes or select an existing transport from an already created node.

Simplified firewall rules result from fewer open ports, reducing complexity. The configuration process is user-friendly, and supported by an assistant in the anynode frontend. Additionally, the feature offers flexible options for node selection based on a customizable whitelist or a transferred local SIP domain.

In a company operating several nodes in its communication infrastructure, this feature allows these nodes to use a shared SIP transport, making them reachable via the same port. Node usage is decided through a flexibly configurable network peer whitelist in the SIP node object or based on the request URI domain or the remote end’s TO header.

Characteristics

Enables multiple SIP nodes to share a SIP transport
Accessible via the same port
Configurable node selection via whitelist or local SIP domain
Step-by-step configuration through Node assistant

Benefits

Reduced port consumption
Simplified firewall rules
User-friendly configuration
Flexible node selection options

anynode – The Software SBC object structure for port sharing.

Animation: The node wizard asks whether a new SIP transport should be created that can later be used by other nodes. An existing SIP transport from an already created node can also be selected.

The node wizard asks whether a new SIP transport should be created that can later be used by other nodes. An existing SIP transport from an already created node can also be selected.

Screenshot: An incoming call can be assigned to a specific node in the SIP node settings. At least one of the following two criteria must then be met: Match of the Local SIP Domain and Match with the initial INVITE message in the Network Peer Whitelist

An incoming call can be assigned to a specific node in the SIP node settings. At least one of the following two criteria must then be met: Match of the Local SIP Domain and Match with the initial INVITE message in the Network Peer Whitelist

Screenshot: SIP node object settings for shared SIP user agent objects in anynode – The Software SBC.

The node wizard asks whether a new SIP transport should be created that can later be used by other nodes. An existing SIP transport from an already created node can also be selected.