By default, your Zeacom server will use UDP to communicate with the client applications, on the various workstations within your Local Area Network (LAN). UDP is the default method, because it's quicker and lighter than TCP and ties up less network bandwidth. UDP uses a simple transmission model without implicit hand-shaking for assured reliability, ordering, or data integrity. As a result, UDP provides an unreliable service and datagrams may arrive out of order, appear duplicated, or go missing without notice. UDP assumes that error checking and correction is either not necessary or performed in the application, avoiding the overhead of such processing at the network interface level.

However - there is another way!

Sometimes UDP simply isn't considered good enough for the end-user - most usually intensive telephone users, such as receptionists using Console, or agents using Desktop. You may find users such as these sometimes complain a call looks like it's still in progress when it's not - or a call timer is still counting up, whilst the actual call has ended. This is because UDP packets are sometimes being dropped and the Server's announcement that things have happened haven't reached the clients!

Secondly, UDP traffic is also not passed on by your Default Gateway, or Router - therefore if you happen to be attempting to run a Zeacom application outside of the LAN, then it won't work. If you work from home, or outside of the office, and are lucky enough to have some way into the LAN - such as a VPN, then you may wish to run Desktop or other CTI applications from your computer, whilst outside of the office.

For both these situations, you can force your client computer to establish a TCP connection to the Zeacom server - ensuring that all packets are sent and recieved (TCP includes Error Checking), and is also able to traverse gateways and routers.

To do so, open notepad and paste in the items in this document which are in yellow. Then save the file as a .reg file. Once saved, double click and it will be imported into your registry and force your Zeacom applications to create a TCP connection to their server. Please note, before saving the file you must ammend the two IP addresses within the items in yellow with the STATIC IP of your Zeacom Server.

[HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient] [HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\AutodiscoveryInterfaces] [HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\AutodiscoveryInterfaces\[Default]] [HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\AutodiscoveryInterfaces\[Default]\ClientAutodiscoverySocket] [HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\General] [HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\PrimaryInterfaces] "InterfaceList"="Main" [HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\PrimaryInterfaces\Main] "IsBroadcastSocket"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\PrimaryInterfaces\Main\BroadcastSocket] [HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\PrimaryInterfaces\Main\OutboundSocket] "PeerAddress"="STATIC IP" [HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\PrimaryInterfaces\[Autodiscovery]] "InterfaceList"="" [HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\PrimaryInterfaces\[Autodiscovery]\BroadcastSocket] [HKEY_LOCAL_MACHINE\SOFTWARE\Zeacom\IpcClient\PrimaryInterfaces\[Autodiscovery]\OutboundSocket] "PeerAddress"="STATIC IP"

Note, if you're utilising a Zeacom 2.x, or 3.x installation, the key above will not work.