Signaling library timeouts are applicable only to functions that
are at the receiving end of a request, confirm or indication primitive.
They can be of the following types:
- Request receptions
- These occur on the side of the signaling process, which typically
polls for them in accordance with the message communication protocol
applied by the signaling library. In effect this corresponds to an
infinite timeout.
- Confirm receptions
- These occur on the side of the application, which waits for a
message from the signaling process to confirm a request it has just
sent to it. For all requests (except SL_ABORT_REQ), the application
times out if it does not receive a confirm message within 120 seconds.
It then sends an abort request as described earlier. After a further
four seconds the application times out again if it does not receive
a confirm answer from the signaling process, and an error is reported.
- Indication receptions of call setup information
- Message information timeouts for common channel signaling protocols
such as ISDN and SS7 are zero because signaling processes for these
can control when they write the call information, and this is done
before the indication is sent. Exchange data link timeouts can be
from 3 to 10 seconds (the default is 5)—see the Blueworx Voice Response for AIX:
Configuring the System information for details of the
EDL Message Info Time Out (Seconds) system parameter.
- Indication receptions of call disconnect information
- Only common channel signaling processes can now send information
relating to far-end (network) hangups. This information is written
before the indication is even sent (so the timeout is zero) and is
accessible immediately at the application level under system variable
SV543.