
Avaya Media Processing Server Series System Reference Manual
Page 234 # P0602477 Ver: 3.1.11
Application-Host Interaction Configuration Options
The following discussion is an overview of the essential aspects of programming an
application for VTCPD communications from a configuration perspective. Typically,
PeriProducer applications are programmed to perform the following steps in the
indicated order using the functions of the Resource block:
• acquire the VTCPD resource (GET),
• send a message to the host (SEND),
• receive a reply from the host (RECEIVE),
• free the VTCPD resource (FREE).
This entails having VTCPD reserve an available host connection (the slot), send data
to the host (associating the ID field with the phone line), receive data from the host
based on the specified ID, and then release the slot.
After a successful attempt to acquire a VTCPD slot, the application receives the
condition gotres. Data associated with the condition contains the connection
number, slot number, and VTCPD port number in the format XXX:YYY:ZZZ. The
application does not need to process this data.
If a reply from the host arrives before the application issues the RECEIVE command,
the reply is held by the VTCPD daemon. If the application terminates, the slot is
released automatically.
Regardless of the message format, the SEND request should include only the
data portion of the message, because the delimiter (-f | -F d) or length header
(-f | -F l) is provided by VTCPD.
It is possible after the initial SEND request to mix SEND and RECEIVE requests in
any order. The message ID of the last SEND is always in effect (until the slot is freed)
and can be used to identify consecutive RECEIVEs.
For example, in the following scenario, the application receives two messages with
the specified ID-field:
• acquire the VTCPD resource,
• send a message to the host,
• receive a reply from the host,
• receive a second reply from the host,
• free the VTCPD resource.
During the interval between acquiring the resource (GET) and when the resource is
released (FREE or STOP), the slot is reserved exclusively for that application line.
If the size of the slot pool is limited, it may be necessary to reserve the slot for a
shorter period of time. If an application does not use GET (i.e., only executing SEND
and/or RECEIVE requests), the slot is released as soon as the host data arrives.
Komentáře k této Příručce