User`s guide

In the third case, a custom Neuron Chip application must be written.
All three cases could be used with the same SLTA-10 Adapter.
In the dial-out only case, besides the call initiation, the SLTALink Manager must be
able to launch the appropriate application - with the correct database and device
driver name. One system solution is to create a separate link for each SLTA-10
Adapter. Each link then stores the Remote Identifier of its SLTA-10 Adapter after
the first connection. Upon connection, the appropriate application and command line
arguments stored in the link get launched. A second viable approach is to create a
generic link that uses the wild card as a Remote Identifier to launch a generic
application using command line arguments to specify the appropriate network or
database and device driver name. These arguments are available and described
above under Invoking an Application.
Note: if the device driver information used in the application does not
match the device driver name being used by the link, the newly launched
application can open a second device driver - which may result in an
attempt to dial-in to the network. Since the modem is still presumably in
use with the original dial-out call to the host PC, the second call will fail.
The result is a system-level failure.
Dial-In / Dial-Out
These scenarios are the combinations and permutations of the above. However, it
needs to be pointed out that not all dial-in strategies can co-exist with all dial-out
strategies. For example, if the dial-out strategy involves having the SLTALink
Manager match the incoming call to the wild card Remote Identifier and if the dial-in
strategy requires a separate link for each SLTA-10 Remote Identifier, then it is
possible that a call initiated from the network will be received by the SLTALink
Manager and will be matched with the link created for the dial-in case.
The correct
application may not be launched and a system-level failure may occur.
Callback
The SLTA-10 Adapter callback functionality works as follows: A call is initiated from
some remote PC to an SLTA-10 Adapter on a network, which must have its NSI
mode EEPROM configured to require callback. The SLTA-10 Adapter answers; the
remote PC identifies to the SLTA-10 Adapter one of the SLTA-10 Adapters directory
entries to use for the callback. An SLTA-10 configured to require a callback will not
accept any other direction from the host at this time. The original call is terminated,
and the SLTA-10 Adapter calls the phone number indicated in its directory. Note:
this does NOT need to be the phone number of the original remote PC that initiated
the call. Typically, the SLTALink Manager on the remote host dialed answers the
call and launches the appropriate application.
Several possible system-level failures include:
l The original remote host expects to receive the callback, but the directory index
reflects the phone number of another remote host.
l The original remote host application opens an LNS database and initiates the
first call. The callback is directed back to the original remote host PC. The
7-16
SLTA-10 NSI Mode Software