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
-
If the computer on which Security
Desk is running provides
multiple network interfaces (cards), verify that the network interface used for
Sipelia™ is selected.
-
Verify that the RabbitMQ Server is installed and is running on both the client
(Security
Desk) and server
(Sipelia™ Server).
-
Log on to Security
Center with Config
Tool.
-
Select the Sipelia™ plugin role, and
verify that the role is up and running.
-
Click General, and make sure that the address and port
properties are set to the proper values.
-
Click Servers, and make sure that SIP
port is set to the proper value.
-
Make sure that the ports are not being blocked anywhere on the network.
-
Open the Network task, and then select the server that is
hosting the Sipelia™ plugin role.
-
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.
-
Log on to Security
Center with Security
Desk.
-
Click , and make sure that UDP port range is set
properly.
-
On the Sipelia™ Server,
browse to folder C:\ProgramData\Genetec Sipelia\SipServer
and open SipServer.config.
-
Make sure that MinimumPortRange and MaximumPortRange values are
set properly in the file.