Lines Matching full:application

53 If the application wants the \fBSIP\fR stack to maintain dialogs, this flag
101 This is a mandatory routine that the application registers for the stack to
106 The \fBSIP\fR message is freed once the function returns. If the application
108 message using \fBsip_hold_msg()\fR. Similarly, if the application wishes to
123 An application can register these two routines to implement its own routines
124 for the stack timers. Typically, an application should allow the stack to use
126 the stack and are not available to applications. If the application registers
129 These functions must be registered for single-threaded application. Otherwise,
140 The application can register this routine to be notified of a transaction
153 An application can register this routine to be notified when a dialog is
175 The connection manager interfaces must be registered by the application to
177 connection object that is defined by the application. The application registers
179 object is application defined, but the stack requires that the first member of
230 The application provides a mechanism for the stack to indicate that a
235 application will not free the connection object if it is in use by the stack.
307 These four interfaces may be registered by an application to provide connection
320 In addition to the \fBSIP\fR headers supported by the stack, an application can
323 headers supported by the stack, parsing functions or other application-specific
352 The full name of the header. The application must ensure that the name does not
354 application takes precedence.
391 An application can optionally provide this function that will check if the
393 by the application.
402 An application can optionally provide this function to determine whether two
404 application.