Lines Matching refs:TRYING
127 * | Trying |-------------+
317 * This timer task is for INVITE server transactions. It will send a trying in 200 ms. if the
334 if (realState == null || TransactionState.TRYING == realState) {
336 sipStack.getStackLogger().logDebug(" sending Trying current state = "
340 .createResponse(100, "Trying"));
342 sipStack.getStackLogger().logDebug(" trying sent "
346 sipStack.getStackLogger().logError("IO error sending TRYING");
595 // that it is trying to cancel.
666 * Send out a trying response (only happens when the transaction is mapped). Otherwise the
670 // note that TRYING is a pseudo-state for invite transactions
674 if (realState == null || realState == TransactionState.TRYING) {
675 // JvB: Removed the condition 'dialog!=null'. Trying should also
682 // TU did not send a trying in that time.
727 this.setState(TransactionState.TRYING);
731 // Rsends the TRYING on retransmission of the request.
739 sendMessage(transactionRequest.createResponse(100, "Trying"));
912 // trying state,
914 if (getRealState() == TransactionState.TRYING) {
918 // INVITE ST has TRYING as a Pseudo state
919 // (See issue 76). We are using the TRYING
922 // has sent trying or not and hence this
952 // PROCEEDING case below. There is no TRYING state for INVITE
1175 && (TransactionState.CALLING == this.getRealState() || TransactionState.TRYING == this
1328 // Trying to send final response and user forgot to set
1427 * Invite transactions do not have a trying state. We just use this as a pseudo state for
1433 // Trying is a pseudo state for INVITE transactions.
1434 if (this.isInviteTransaction() && TransactionState.TRYING == super.getState())
