Security Desk cannot connect to Sipelia Server - Sipelia™ 2.6

Sipelia User Guide 2.6

series
Sipelia™ 2.6
revised_modified
2017-11-13

If Security Desk cannot connect to the Sipelia Server, verify that the IP address and port properties are properly set.

What you should know

Connection issues typically occur when IP addresses or ports are not configured properly, or when the network is blocking packets from being exchanged between two endpoints.

Procedure

  1. If the computer on which Security Desk is running provides multiple network interfaces (cards), verify that the network interface used for Sipelia™ is selected.
  2. Verify that the RabbitMQ Server is installed and is running on both the client (Security Desk) and server (Sipelia Server).
  3. Log on to Security Center with Config Tool, and then open the Plugins task.
  4. Select the Sipelia™ Plugin role, and verify that the role is up and running.
  5. Click General, and make sure that the address and port properties are set to the proper values.
  6. Click Servers, and make sure that SIP port is set to the proper value.
  7. Make sure that the ports are not being blocked anywhere on the network.
  8. Open the Network task, and then select the server that is hosting the Sipelia™ Plugin role.
  9. Click Properties, and make sure that the first IP address shown in Private addresses, that is, the IP address listed at the top, is the one that you want to be used by the server.
    Sipelia Server automatically uses the first IP address shown in the list.
  10. Log on to Security Center with Security Desk.
  11. Click Options > Sipelia > Advanced, and make sure that UDP port range is set properly.
  12. On the Sipelia Server, browse to folder C:\ProgramData\Genetec Sipelia\SipServer and open SipServer.config.
  13. Make sure that MinimumPortRange and MaximumPortRange values are set properly in the file.