Lines Matching defs:in
7 * employees are not subject to copyright protection in the United States
8 * and are considered to be in the public domain. As a result, a formal
76 * {@link javax.sip.SipStack} ). In addition to these, the following are
77 * meaningful properties for the NIST SIP stack (specify these in the property
85 * </b> This property is used by the built in log4j based logger. You can use
88 * logged in SERVER_LOG. If you set this to 32 and specify a DEBUG_LOG then vast
89 * amounts of trace information will be dumped in to the specified DEBUG_LOG.
101 * </code> allows you to now control logging in the stack entirely using log4j
121 * Otherwise messages are logged in a format that can later be viewed using the
122 * trace viewer application which is located in the tools/tracesviewer
164 * : If the request has no tag in the To header field, the UAS core MUST check
167 * does not match that transaction (based on the matching rules in Section
179 * controlled as follows : If the previous in-DIALOG request was an invite
182 * in-DIALOG transaction was a INVITE ServerTransaction then Dialog waits for
191 * If set to false (the default), the application does NOT get notified when a Dialog in the
192 * NULL state is terminated. ( Dialogs in the NULL state are not associated with an actual SIP Dialog.
193 * They are a programming convenience. A Dialog is in the NULL state before the first response for the
195 * when a Dialog in the NULL state is terminated.
222 * event delivered to the listener is run in the context of a new thread.</li>
229 * machine but will run the listener in its own thread.</li>
236 * transactions may concurrently receive messages and this will result in
237 * multiple threads being active in the listener at the same time. The listener
238 * has to be written with this in mind. <b> If you want good performance on a
247 * high water mark. Requests are selectively dropped in the lowater mark to
255 * (i.e. it does its own resource management in the application).</li>
269 * result in a memory leak.
275 * transactions can be handled uniformly in user code during cleanup), then set
280 * server. This defines the timeout in miliseconds between successive reads
282 * headers must be delivered in this interval and each successive buffer must be
283 * of the content delivered in this interval. Default value is -1 (ie. the stack
312 * health of its internal threads (the property specifies the time in
315 * an exception or getting stuck in a deadlock condition. Events like these will
319 * remain disabled. An example of how to use this property is in
329 * parameter in the Message. Otherwise, it will use the content length supplied
334 * Default is <it>true</it>. This flag is added in support of load balancers or
341 * has been Terminated. Clearly this will result in protocol errors. Setting the
350 * controlled as follows : If the previous in-DIALOG request was an invite
353 * in-DIALOG transaction was a INVITE ServerTransaction then Dialog waits for
363 * is a big number in the order of 8*8*1024.</li>
370 * is a big number in the order of 8*8*1024 or higher.</li>
394 * When a forked response is received in this time interval from when the original
396 * client transction in the ResponseEventExt and deliver that to the application.
408 * (client and server) will use the key store provided in the fileName. The
422 * <b> Note that the stack supports the extensions that are defined in
423 * SipStackExt. These will be supported in the next release of JAIN-SIP. You
424 * should only use the extensions that are defined in this class. </b>
540 // In version 1.2 of the spec the IP address is
1004 InputStream in = getClass().getResourceAsStream("/TIMESTAMP");
1005 if (in != null) {
1007 new InputStreamReader(in));
1011 if (in != null) {
1012 in.close();
1157 // Stop the message processing thread in the listening point.
