Settings

General server settings

bg-dots
bg-dots

The System → Settings section configures the numbering plan, SIP and H.323, NAT, P2P calls, anonymous participants, LDAP, reservation, media server cascading, and network diagnostics.

All conferences must be finished before changing settings; new values apply about one minute after saving.

Main

This tab contains the server’s basic parameters: numbering plan, H.239, SIP (including simultaneous registrations and lost packet recovery), QoS, time, and interface language.

Range id settings

Define the server numbering plan. Ranges are used for automatic account and conference creation and as recommended numbers for manual creation. An account or conference can still be created manually with a number outside the range.

“Prefix” (accounts) – numeric prefix prepended to account numbers. Digits 0–9 only, length from 0 to 10 characters; may be empty.

“from” / “to” (accounts) – account number range. Default 100–999. “to” must be greater than or equal to “from”.

“Prefix” (conferences) – numeric prefix for conference numbers; same constraints as the account prefix.

“from” / “to” (conferences) – conference number range. Default 1000–1999.

“from” / “to” (LDAP) – number range for accounts synchronized from LDAP (including automatic number assignment). Default 2000–2999. If the range is exhausted during LDAP sync, new users are skipped.

H.239 settings

“Send content in mainstream” – server-wide mode: the incoming second stream (content) is sent in the main video stream. Available values: “No”, “Yes”.

Other settings

“Allow to make group calls” – allows WS accounts to make Add-Hoc calls: turn a point-to-point call into a conference by inviting participants from the address book. P2P escalation conditions and differences from Desktop/terminal are in P2P calls and licenses.

“Server name” – display name of the server in the interface and related views.

SIP settings

“Signal port” – SIP signaling port. Default 5060. Changing the port requires the same value on connected devices and in network rules.

“RTP timeout” – timeout waiting for RTP packets, seconds. Default 60. If no media arrives within this time, the session may end.

“Number of simultaneous registrations per abonent” – maximum number of simultaneous registrations of one account from different devices (several clients under one number). Default 10. Exceeding the limit rejects new registrations until a slot is free.

“Encryption” – SIP encryption mode. Available values: “Disabled”, “Enabled”.

“Lost packet recovery” – recovery of lost media packets (LPR) on the server side. Available values: “Disabled”, “Enabled”. When enabled, the effect of packet loss on audio/video quality on unstable links is reduced; when disabled, recovery is off.

Service type

Sets the IP packet quality of service (QoS) level, including when the network is congested.

“TOS decimal” – decimal TOS value. Default 16.

Time settings

“Time zone” – server time zone (selected from the list). Default Europe/Moscow.

“Date and time” – manual date and time of the server.

Interface settings

“Default language” – language of splash screens and voice prompts (purgatory, empty conference, and similar). Available values: Russian, English, Dutch, French, Spanish, German, Vietnamese.

“Save” – save the tab settings.

H.323 settings

This tab configures H.323 signaling, the H.225/H.245 port range, user matching by alias, and gatekeeper operation (internal or external). Gatekeeper status is shown on System → Status.

“Signal port” – H.323 (H.225) signaling TCP port. Default 1720. Changing the port requires the same value on endpoints and in network rules (firewall, NAT).

“RTP timeout” – timeout waiting for RTP packets, seconds. Default 60. If no media arrives within this time, the session may end.

“From” / “To” (port range for H.225/H.245) – port range for H.225/H.245 channels. Default 20000–65000. “To” must be greater than or equal to “From”. The range must be open on network equipment for H.323 traffic.

“Determine users by H.323 alias (aka UserByAlias)” – toggle. Off by default. On: an incoming call is matched to an account by H.323 alias (the number in the account list), not only by IP/transport.

“Use gatekeeper” – gatekeeper mode. Available values:

  • “Don’t use” (default) – the gatekeeper is not started and the server does not register on an external gatekeeper; on System → Status the Gatekeeper status is inactive;
  • “Internal gatekeeper” – enables the built-in gatekeeper on the server; required for registered H.323 accounts;
  • “Register on external gatekeeper” – the server registers on the specified external gatekeeper; additional fields for address, registration alias, and announce options appear on the form.

“Save” – save the tab settings.

NAT

This tab configures server behavior behind NAT: the external address and protocols, local networks without external IP substitution, STUN, the RTP port range, and ICE servers for WebRTC.

NAT settings

“External IP” – public IP address at the NAT border that the server inserts into signaling for external clients. Example: 172.16.0.2. Without a correct external IP, clients behind NAT may receive wrong addresses in SDP/signaling.

“SIP” – toggle: apply NAT substitution for SIP.

“H.323” – toggle: apply NAT substitution for H.323.

“Local networks” – networks for which the external IP is not substituted (traffic is treated as local). One network per line in network/netmask form, for example 10.0.0.0/255.255.255.0. A wrong list causes external IP substitution inside the LAN or the opposite.

Attention!
If “External IP” is set, “Local networks” must list local networks that must not receive the external IP substitution. One network per line. Do not use CIDR.

STUN

“STUN address” – STUN server address. Default 127.0.0.1.

“STUN port” – STUN port. Default 3478.

RTP settings

“Start” / “End” – bounds of the UDP RTP port range. Default 20000–65000. Values are selected from a list (step 1000). The range must be open on the firewall and NAT for media; a range that is too narrow limits the number of concurrent streams.

WebRTC ICE servers

“List of ICE servers” – JSON array of RTCIceServer objects (STUN/TURN for WebRTC). Default empty array. Invalid JSON is not applied; an empty list means no extra ICE servers from this field. Example:

[
   {
       "urls": "stun:stun.vinteo.com:3478"
   }
]

“Save” – save the tab settings.

P2P

This tab controls recording and handling of P2P (point-to-point) video calls, including the ringing/hold video and Websocket signaling proxying.

“On” – P2P video call recording. On by default. Off — P2P recording is not performed.

“Resolution” – recording video resolution. The list includes, among others: UltraHD(4K) 3840×2160, FullHD 1920x1080, HD 1280x720, VGA 640x480, CIF 352x288, and other common modes. Higher resolution increases recording size and disk load.

“Video-on-hold p2p calls” – video shown to the caller while waiting for an answer. Available values depend on uploaded video clips; also “Not selected”.

“Auto loop” – loop the waiting video. Off by default.

“Proxy websocket clients P2P calls” – P2P signaling of Websocket clients goes through the server; media goes directly between endpoints. Off by default. With proxying enabled, soft↔soft (WebRTC) does not use MCU hardware and is not counted as a conference; license use in other scenarios is described in P2P calls and licenses.

Attention!
When “Proxy websocket clients P2P calls” is on, P2P call recording is not available.

“Save” – save the tab settings.

Anonymous connection

This tab sets default parameters for anonymous participants (SIP/H.323 and WS), H.323 encryption, RTP filtering, anonymous access rights, and the codec set.

“Bandwidth for SIP and H.323 participants” – maximum bitrate for anonymous SIP/H.323 participants. Values from 64 Kb/s to 10 Mb/s (including 1.5 Mb/s).

“Resolution for SIP and H.323 participants” – video resolution for anonymous SIP/H.323. List of common modes (UltraHD, FullHD, HD, CIF, and others).

“FPS for SIP and H.323 participants” – frame rate. Available values: 15, 25, 30, 60.

“Bandwidth for WS participants” / “Resolution for WS participants” / “FPS for WS participants” – the same parameters for anonymous WebSocket (web client) participants; value sets match SIP/H.323.

“Create an anonymous room” – create a temporary conference (room) if it does not exist yet. Off by default.

“H.323 Crypto” – H.323 encryption for anonymous connections. On by default.

“Filtering RTP” – block extra media streams from the same port (RTP protection). On by default.

“Allow anonymous connection to the server” – accept anonymous calls to the server (SIP/H.323/WebRTC without an account). On by default.

“Allow anonymous connections to auto attendant” – an anonymous caller may enter the auto attendant and then a conference. On by default.

“Allow anonymous connections to call accounts” – an anonymous caller may call registered accounts. Off by default.

“Codecs” – allowed codecs for anonymous connections; selection by moving items between lists (audio/video, including h264, h265, opus, vp8, vp9, g722, and others).

“Save” – save the tab settings.

LDAP

This tab configures directory service integration. To enable synchronization, save the settings and run a connection check.

“Turn on account synchronization over LDAP” – starts account import from the directory. Off by default: with the toggle off, settings can be saved and checked, but accounts are not imported. Enable after a successful “Connection check”.

“Server IP” – address of the domain controller or LDAP server. Accepts IPv4 (10.0.0.5) or a DNS name (dc01.example.com). The server uses this address for the connection check and synchronization. A wrong address or unreachable host causes a connection error; the host name must resolve from the VCS server.

“Server port” – TCP port of the LDAP/LDAPS service. Default 389. The port is not changed automatically when “Encryption” changes — set it manually. Typical values: 389 for plain LDAP (None and TLS modes); 636 for LDAPS when encryption is SSL. A mismatch between port and encryption causes a connection failure.

“Scheme” – directory attribute model. Possible values:

  • ActiveDirectory (default) — for Microsoft AD; default filter (&(objectclass=user)(objectcategory=person)(!(objectclass=contact))); AD attributes are used (objectcategory, userprincipalname, and others);
  • OpenLDAP — for OpenLDAP; default filter (&(objectclass=inetorgperson)(objectclass=person)); objectclass is used instead of objectcategory, user class is inetorgperson;
  • FreeIPA — for FreeIPA; default filter (&(objectclass=organizationalPerson)(objectclass=person)).

A scheme that does not match the real directory yields an empty result set or search errors even when IP, port, and credentials are correct.

“Encryption” – channel protection to the directory. Possible values:

  • None (default) — no encryption, usually with port 389; acceptable only on a trusted network;
  • TLS — StartTLS: the connection starts on the LDAP port (usually 389), then upgrades to TLS;
  • SSL — LDAPS: encryption from the start of the session, usually port 636.

Encryption affects only how the connection is established, not which fields are imported.

“User” – account with directory read rights used for bind and search. The format depends on the directory and on “User prefix” / “User suffix”: full UserPrincipalName (vinteo-ldap@example.com), short login when a suffix is set (vinteo-ldap), full DN (CN=vinteo-ldap,OU=Service,DC=example,DC=com), or for OpenLDAP a login combined with prefix and suffix. Without a successful bind, synchronization and the connection check are impossible.

“User password” – password for the account in “User”. An empty value is not allowed on the first save; on later saves the field may be left empty to keep the stored password unchanged.

“Base DN” – search root for accounts. Examples: OU=Users,DC=example,DC=com, DC=example,DC=com, for OpenLDAP — ou=people,dc=example,dc=com. Search runs only inside this branch: a narrower DN reduces the selection scope and load; a DN that is too narrow excludes users from other OUs; an empty or wrong DN causes an error or an empty result.

“Search filter” – LDAP filter for selecting users. Possible options:

  • empty field (default) — uses the built-in filter of the selected “Scheme” (see above);
  • custom filter — fully replaces the scheme filter and defines whom to import.

The filter does not depend on account type (WS / Loop). Custom filter examples:

  • mail required — (&(objectclass=user)(objectcategory=person)(mail=*));
  • only an AD group — (&(objectclass=user)(memberof=CN=VinteoUsers,OU=Groups,DC=example,DC=com));
  • exclude disabled AD accounts — (&(objectclass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2))).

“Username attribute” – directory attribute whose value becomes the LDAP account identity and is used for authentication. Default userprincipalname (typical for AD). Other common values: uid (OpenLDAP/FreeIPA), sAMAccountName, mail, dn. A record without this attribute is not imported.

“User prefix” – string prepended to the login on bind. Empty by default. For OpenLDAP often uid= or cn=. For Active Directory it is usually left empty. A wrong prefix breaks authentication of the service account and of imported users.

“User suffix” – string appended after the login on bind. Empty by default. Typical values: @example.com (AD UPN suffix) or ,ou=people,dc=example,dc=com (DN tail in OpenLDAP). If empty, “User” must enter the full name with domain (or a full DN). If set, a short name is enough. A wrong suffix causes a bind error.

“User number attribute” – directory attribute used as the VCS account number. Examples: ipPhone, telephoneNumber, mobile. Used when WS “Assign numbers automatically” and “Use a userPrincipalName attribute as a number” are off. If the attribute is empty for a user in the directory, the record is not imported. When those WS toggles are on, the field is disabled in the UI.

“Account type” – type of created accounts. Possible values:

  • Loop (Skype4b) (default) — accounts for Skype for Business; the auto-number, UPN-as-number, and auto-registration toggles are hidden;
  • WS (web client) — accounts for the web client and Vinteo Desktop; the three toggles below become available.

“Assign numbers automatically” – toggle (WS type only). Off by default: the number is taken from “User number attribute” (unless UPN mode is on). On: numbers are assigned sequentially from the LDAP range on the “Main” tab; the directory number attribute is not used and the attribute field is disabled. If the range is exhausted, new users are skipped during synchronization.

“Use a userPrincipalName attribute as a number” – toggle (WS only). Off by default. On: the number is the UPN part before @ (user@example.com → user); “User number attribute” is disabled. Not suitable if the UPN local part has invalid characters or matches an already used number — such a record is skipped.

“Allow automatic registration” – toggle (WS only). Off by default: the account can register on the server only after being added to a conference. On: registration is allowed immediately after import, without first adding the account to a conference.

Notice:

These three toggles are available only for WS account type.

To test the connection, fill in the parameters, then click “Save” and “Connection check”. After a successful check, enable “Turn on account synchronization over LDAP”.

“Purge LDAP users” – deletes accounts previously synchronized from LDAP (local accounts are not affected).

Attention!

There are several conditions for correct import of user data:

  • A sufficient range of numbers for LDAP accounts must be allocated in the numbering plan (see the LDAP parameter on the “Main” tab).
  • Records without a value in the login attribute (default userprincipalname), without a display name (displayName), or without an account number are not imported; an empty mail attribute alone does not block the import.
  • Only one LDAP server can be connected.
  • A filter that is too narrow reduces the import list; a syntax error causes the search to fail.

Example procedure

Example settings:

  • “Server IP” – dc01.example.com (or the domain controller IP);
  • “Server port” – 636;
  • “Scheme” – ActiveDirectory;
  • “Encryption” – SSL;
  • “User” – ldap-sync (a service account with directory read rights);
  • “User suffix” – @example.com;
  • “Base DN” – OU=Users,DC=example,DC=com;
  • “Search filter” – empty (the scheme filter is used);
  • “Username attribute” – userprincipalname;
  • “Account type” – WS (web client);
  • “Use a userPrincipalName attribute as a number” – on;
  • “Allow automatic registration” – on.

With these settings the server does the following.

Connection. Connects to Active Directory over LDAPS (port 636, SSL encryption). Search starts at Base DN OU=Users,DC=example,DC=com and covers the whole subtree.

Selection. “Search filter” is empty, so the Active Directory scheme filter is used:

(&(objectclass=user)(objectcategory=person)(!(objectclass=contact)))

User objects (user / person) are selected; contacts are excluded.

Processing on the server. Only records with both userPrincipalName and displayName are imported. An empty mail does not block the import. With “Use a userPrincipalName attribute as a number” on, the account number is the UPN part before @ (for example, user@example.com → user).

“Save” – save the tab settings.

Reservation

This tab configures server reservation (second node) parameters.

Attention!
After saving reservation settings, the IP address configured on network interface eth0 becomes unavailable.

“IP” – IP address of the backup server’s second interface. Used for service exchange between the primary and backup nodes. An incorrect address or unreachable node prevents building a reservation pair.

“Save” – save the tab settings.

Cascading

The “Media server list” block configures media servers (MCU) for cascading and capacity failover: addresses, ports, password, and switching to a backup MCU.

“Add” – add a media server card to the list.

For each server (for example “Server #1”):

“Server name” – media server name (Latin letters). Form example: localmcu.

“IP” – media server address. Typically 127.0.0.1 for a local MCU.

“Port” – MCU incoming connection port. Default 5000.

“Backup Port” – backup MCU port. Default 5001.

“Local IP” – address of the master (control) server that connects to the media server.

“Password” – administrator password of the remote/media server for the service connection.

“Processor” – processor binding. Available values: “All”, “Processor #1”.

“Debugging mode for the main MCU” – toggle for extended main MCU debugging. Off by default.

“Status” – connection state to the media server (indicator on the card).

“Switch to a backup MCU” – switch operation to the backup media server (via “Backup Port”).

Deleting a card — the red trash-icon button on the server card.

“Save” – save the media server list.

Diagnostics

This tab is used to check the network from the VCS server. It has two tools: “Ping” and “Traceroute”.

Ping

ICMP reachability check from the VCS server: packet loss, latency (RTT), TTL.

“IP” – IPv4 address or DNS name of the host. Example: 10.0.0.1.

“Ping” – run the check. While it runs, a progress indicator is shown. When finished, the full reply text appears below the form (as from the ping utility): a PING … header, bytes from … icmp_seq=… time=… lines, and a statistics block (packets transmitted / received / % packet loss, rtt min/avg/max).

Typical use: verify reachability of a gateway, DNS, LDAP controller, or remote endpoint from the server. Unreachability or high packet loss / RTT points to a network issue on the path from the server to the host.

Traceroute

Build the hop path from the server to the specified host.

“IP” – IPv4 address or DNS name (same as Ping).

“Traceroute” – run traceroute. The result appears below the form: a traceroute to … header, then hop lines with names/addresses and response times (ms). A break or timeouts at a hop help locate where traffic is lost.

Gateways Incoming calls