3
Introduction
DSS 5 servers require bi-directional (Bidi) communication between the server and managed devices for
most DSS functions to operate properly. In this context communication means that one endpoint of the
communication (either the DSS server or the device) can initiate a TCP-IP communication with the other
endpoint. For example, if the DSS server initiates a communication with a device and the device is able
to answer during the same communication session this does not prove bi-directional communication,
this would only be considered uni-directional communication from the DSS Server to the Device. For the
communication to be bi-directional the device would also have to be able to initiate a communication
session with the DSS Server.
DSS servers communicate with FutureSmart devices over TCP port 7627. DSS servers communicate with
pre-FutureSmart devices over port 1783.
Symptoms of Bidi Problems
If communication between the DSS server and the device are blocked in both directions the
administrator will get an “unable to communicate” error when trying to add the device, or while
performing a Status update to an already bound device.
It is possible for a device to be added to DSS with only uni-directional communication enabled from the
DSS server to the device. If this is the case there will be problems encountered with job processing later
when end users try to send jobs from the devices. Jobs will fail. There can be others errors as well, such
as the auto-completion of email addresses will fail.
Testing
Starting with DSS 5.01.02 the automated and manual testing of bidi communication has been
implemented and/or improved from past versions. The available tests change depending on device type:
FutureSmart or pre-FutureSmart.
FutureSmart Devices
Automated testing has been added to the system for testing bidi communication with FutureSmart
devices. Every time the DSS service is started, DSS will do a bidi test with the first FutureSmart device
added to DSS. The test will wait up to 1 minute for the device to do its part to initiate a conversation
with the DSS server, if that conversation is not started within 1 minute the test fails and the
administrator is informed of the failure. If the test passes it typically will not add more than 5 seconds to
the device add process.
A manual test has also been added that can be run on FutureSmart devices. This is to cover the scenario
where the administrator feels bidi communication may be an issue after the system has done its single
automated test. To run the test, from the Device Configuration tab of the Configuration Utility, right
click on the device to be tested. In the menu that opens select the “Verify bidirectional connection”
item.
Comentários a estes Manuais