Installation guide

Diagnostics

Problem when pushing from BlipNet to an OPP server device

If pushing from a BlipNet to a terminal having the OPP service fails, several possible reasons

exist. Problems might occur at different levels in the push phase. Before going through this

procedure please make sure that the correct configuration is used. Either the “Object Push

Client”, the “T68i WAP Terminals” or another suitable custom configuration must be used.

If the problem remains then the procedure to find the problem depends on where in the

process it fails. The following problems and solutions are known:

If the BlipNode never finds any devices. Please make sure that the devices to be

pushed to are discoverable. This can normally be configured in the menus on the

device itself.

If the BlipNode does not connect to the device. This may be due to several reasons:

a. The device is in the “BlipServer Disallowed Terminal List” or in the “BlipNode

Disallowed Terminal List” for the specific BlipNode. Please make sure that this

is not the problem. Please see section BlipServer Properties -Allowed

Terminals and section BlipNode Properties - Allowed Terminals.

b. The device did not have the services required. If the remote device did not

have the OPP server, it is simply impossible to push to the device.

Verify that Terminal Types / Services for allowed terminals are configured

correctly, see the Terminal Filtering Wizard section Terminal Types and section

Terminal Services.

If a device did not have the “Required Services”, the BlipNode will put the

device in a local disallowed list (this cannot be seen anywhere in the

BlipManager). Restarting the BlipNode can only clear this local disallowed list.

This functionality has been implemented to prevent an endless loop of failed

SDP searches.