Skip to content

Latest commit

 

History

History
21 lines (18 loc) · 1.79 KB

Configuration_SIP_network_transports.md

File metadata and controls

21 lines (18 loc) · 1.79 KB
Raw

The system supports many network transports for the SIP signaling protocol and content sharing. The network connections are declared using transport configuration entries.

transport = udp;*;20060;*
transport = ws;*;20060;4
transport = wss;*;20062;*
transport = tcp;*;20063
transport = tls;*;20064;*
transport = http;*;20065
transport = https;*;20066

Configuration 2: Signaling (SIP) transports

Format: protocol-value;ip-address-value;port-value;ip-version-value.

  • protocol-value must be udp , tcp , tls , ws, wss, http or https. ws protocol defines WebSocket and wss the secure version (requires OpenSSL). At least one WebSocket transport must be added to allow a web browser (WebRTC SIP client) to connect to the system. The other protocols (tcp, tls and udp) are used for SIP-legacy devices or PSTN.
  • local-ip-value is any valid IPv4/IPv6 address or FQDN. Use star (*) to let the system choose the best local IP address to bind to. Examples: udp;*;5060 or ws;*;5061 or wss;192.168.0.10;5062
  • local-port-value is any unused local port to bind to. Use star (*) to let the system choose the best unused port to bind to. Examples: udp;*;* or ws;*;* or wss;*;5062
  • ip-version-value defines the IP version to use. Must be 4, 6 or *. Star (*) is used to let the system choose the best one. Using star (*) only make sense if local-ip-value is a FQDN instead of IP address. A transport configuration entry must have at least a protocol, IP address (or star) and port (or star). The IP version is optional.
    udp , tcp , tls , ws and wss protocols are used to transport SIP messages while http and https are used to upload presentations.