Mesh functionality is necessary when you want to combine two or more estos UCServer (only within one local network) into one group. Note that the mesh only provides the infrastructure within which you can set up other services/features/functions.

Technically speaking, the mesh is implemented through bidirectional connections. Every estos UCServer participating in the mesh (below described as Mesh Node) is connected to every other mesh node in such a way that messages can be mutually exchanged. One of the two mesh nodes connects (in the client role, technically speaking) to the UC client network interface of the other mesh node. TCP or TLS is used as a protocol here, depending on how Client Network Interfaces is configured.

Rules for protocol selection:
  • If TLS can be negotiated as a protocol, then TLS is used.
  • If one of the two mesh nodes in the client network interface has set encryption type STARTTLS required, only a TLS connection will be established (otherwise errors will arise, e.g. if the server certificate has not been rated as trustworthy by both sides).

In the Administrator you'll find settings for Mesh. The most important settings are:
  • Automatically search for mesh nodes in network
    If activated, the application intermittently searches for other mesh nodes in the network and displays these in the mesh node list. Only those mesh nodes whose mesh ID and password are identical to the personal node are displayed.

  • Mesh ID and password
    All nodes in a mesh have the same mesh ID/password. You can use different mesh IDs to connect multiple separate meshes in a local network.

  • Own mesh node
    Every mesh node is defined by a computer name and port. The node ID shown here describes the separate mesh node.

  • Mesh nodes
    This list displays all other mesh nodes (defined by computer name and port) which exist in the mesh.
    The checkbox right at the front allows you to specify whether a connection is made with this mesh node.
    The status of the connection can be green (connection established successfully) or yellow (error while establishing connection).

    Mesh nodes are sorted into two groups:

    • permanently configured nodes:
      These mesh nodes may be added manually. They will be saved when estos UCServer terminates, and will be available the next time estos UCServer starts.

    • automatically found nodes: These mesh nodes were automatically found in the network, and can be moved to the group described above using the context menu command "Configure this node permanently".

    You may need a separate license to use the mesh functions.
    If mesh functions are not enabled, CallData is not transferred to other estos UCServer.

Version 6.2