Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

Version 1 Current »

You can configure SIP settings in the section for correct SIP server functioning.  After changing any settings, click Confirm at the end of the page.

SIP status 

Here you can monitor SIP proxy and SIP node statuses. Clickto refresh the service.  

SIP settings

In this section, you can cofigure the SIP server. You must enter the following: 

  • only server external IP address if a public server is used; 

  • both server external and internal IP addresses if the server is behind NAT. In this case, server external address is router IP address, and the internal value is the server (computer) IP address where the Link is installed;

  • UDP/TCP port for unencrypted SIP traffic. The default is 5060. For SIP over TLS, port 5061 is used;

  • the maximum bitrate of the transmitted video stream. The default is 512kb/s. 

  • A pool from what RTP ports to what ports are used for audio/video transmission. The default values are from 10000 to 20000.

All ports require forwarding if the server is behind NAT. 

SIP-20220928-223400.png

Network interfaces 

The value of the server external IP address is not required if the Link system is not complex and the server is not behind NAT. If the fields are left blank, the value of the server IP address will be used for them.

You must enter an external IP address, if:

  • the server is behind NAT and one NIC is used. In this case, the IP address of the network card must be entered in both fields;

  • the server is behind NAT and 2 network cards are used:

    • for the internal network in which the door phones are located;

    • for the external network through which the server connects to the Internet.

Internal subnets 

You must enter the address of the subnets in which intercoms and SIP applications of users are connected. The record format is subnet address/mask bit value, for example, 192.168.1.0/24.


SIP nodes 

These settings are required to fill if the container(s) of the SIP nodes are deployed on another server.

If a separate server with a node is behind NAT, then you must:

  • enter the internal/external address of the node;

  • forward a pool of RTP ports for a node.

If a separate server with a node is not behind NAT, then you must specify the external IP address of the node in both fields.

Additional SIP functionality 

Here you can enable the feature of automatic creation of forward rules for apartment group user/s, sending them to device/s (if some devices are added/deleted the corresponding data will be added/deleted to/from devices), and data correction for device/s (if there are some changes in virtual numbers or logical address). 

This feature simplifies forward rules configuration (when it's required to redirect calls from a panel to all user numbers) and management (you don't need to have access to a device to change a rule - it can be done in the Link when editing the group with the device or in the Virtual numbers tab or by the user in the Link app). 

If forwarding rules are already created, be careful when enabling the feature, because automatically created rules may break previously created ones. 

Also, you can delete all created forwarding queues from the server and devices.  

Used ports

The application uses the following ports:

  • 5060 TCP/UDP: unencrypted SIP traffic port;

  • 5061 TCP: port for SIP using TLS;

  • 80 TCP: HTTP port;

  • 443 TCP: HTTPS port;

  • 8443 TCP: port for web SIP caller

  • 10000-20000 UDP: RTP ports for audio/video;

  • 1883 TCP: unencrypted MQTT;

  • 8883 TCP: encrypted MQTT.

If SIP proxies and nodes are running on more than one server with the Link server application, then the following ports must be forwarded to them:

  • 48080: SIP proxy management port;

  • 48081: SIP node management port.

  • No labels