Lines Matching refs:INVITE
78 * |INVITE
80 * INVITE V send 100 if TU won't in 200ms
93 * INVITE V Timer G fires |
120 * Figure 7: INVITE server transaction
317 * This timer task is for INVITE server transactions. It will send a trying in 200 ms. if the
562 // Invite Server transactions linger in the terminated state in the
566 if ((method.equals(Request.INVITE) || !isTerminated())) {
594 // shares the same same branch id of the invite
620 // to be part of an otherwise-matching INVITE transaction.
670 // note that TRYING is a pseudo-state for invite transactions
742 // If an invite transaction is ACK'ed while in
918 // INVITE ST has TRYING as a Pseudo state
920 // pseudo state invite Transactions
933 * From RFC 3261 Section 17.2.2 (non-invite server transaction)
950 // This is the case for INVITE server transactions.
952 // PROCEEDING case below. There is no TRYING state for INVITE
964 * RFC 3261 Section 13.3.1.4 Note, however, that the INVITE server
1044 // If the transaction is not an invite transaction
1047 // This is for Non-invite server transactions.
1165 if ( this.getMethod().equals(Request.INVITE) && sipStack.removeTransactionPendingAck(this) ) {
1195 // Invite transaction is in Confirmed state.
1279 && sipResponse.getCSeq().getMethod().equals(Request.INVITE)
1281 throw new SipException("Contact Header is mandatory for the OK to the INVITE");
1382 } else if (dialog == null && this.getMethod().equals(Request.INVITE)
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.
1614 else if (!this.getMethod().equals(Request.INVITE))
1615 throw new SipException("Request Method must be INVITE");
1675 * When a CANCEL is being processed we take a nested lock on the associated INVITE
1684 * The INVITE Server Transaction corresponding to a CANCEL Server Transaction.
1686 * @param st -- the invite server tx corresponding to the cancel server transaction.
