HP-UX C SIP Stack Programmer's Guide (Novembery 2007)

Creating an Application 39
Getting Module Handles
PROXY
C
ONFIGURATION
The SIP Stack can be used to implement proxy applications. In this case, the
SIP Stack needs to be configured with the isProxy=RV_TRUE parameter and
with all other proxy-related parameters. Fore more information on the proxy
configuration, see the Configuration chapter.
MULTITHREADED
CONFIGURATION
The SIP Stack can be configured to span several internal threads. When working
in multithreaded mode, the main thread inserts events into a processing queue.
The processing threads then take the events from the queue and process them.
Your application should configure the number of processing threads and the
queue size. Fore more information on the multithreaded configuration, see the
Configuration and SIP Stack Threading Model chapters.
GETTING MODULE
HANDLES
In order to use an API of a specific module, you need the manager of that
module. For example, in order to use the Call-leg Manager API, you need a
handle to the Call-legMgr. The Stack Manager API provides functions that
enable you to get the required module handle.
Sample Code
The following code demonstrates how to get the Call-legMgr handle.
/*===========================================================*/
RvSipCallLegMgrHandle AppGetCallLegMgr (
RvSipStackHandle hStack)
{
RvSipCallLegMgrHandle hCallLegMgr;
RvSipStackGetCallLegMgrHandle (hStack, &hCallLegMgr);
Return hCallLegMgr;
}
/*===========================================================*/