| United States-English |
|
|
|
![]() |
hp OpenCall SS7 platform Application Developer's Guide: For Release 3.1 on Linux > Chapter 3 General API GuidelinesIPC Buffers |
|
IPC buffers are used by the HP OpenCall SS7 APIs to communicate with the HP OpenCall SS7 Stack. All the messages that you send or receive from a connection are stored in these internal buffers. You can decide whether messages are buffered before being sent, or if they are automatically flushed to the stack each time the application calls a send() function. By default, HP OpenCall SS7 is set to non-buffering mode, flushing the internal buffers each time a send() is called.
Changing the size of the IPC buffers can optimize the performance of a stack connection because it concatenates the messages contained in the buffer and so reduces the number of IPC calls between processes. You must consider the requirements of the application because increasing throughput will also increase latency. Buffering ModesThe HP OpenCall SS7 APIs support two modes of buffering:
Transit TimeThe application can set the maximum time for which messages can be stored in the API buffer before they are sent. This is known as transit time. Each SS7 stack API allows the application to set the transit time for connections with low and high traffic. Buffer SizesInternal buffer size is defined by the variable FT_BSize in the file global.conf. The default value is 64 Kbytes. This value cannot be changed while the stack is running. IPC buffers can be increased from the default value of 8 Kb. The application can only increase their size to the maximum of 64 Kbytes. These buffers can be sized dynamically by the application by using either SS7_ifctrl() for the MTP, SCCP and OA&M APIs or TCX_control() for the TCAP API. The Internal Buffer size must not be reduced to less than the half of the configured IPC buffer size. For details about the specific IPC functions, see the following API chapters. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||