Class SIP::Transaction::NonInviteServerTransaction
In: sipper/transaction/non_invite_server_transaction.rb
Parent: SIP::Transaction::BaseTransaction

Methods

Included Modules

SipLogger SipperUtil

Attributes

cancel_stxn  [RW]  msg_sent is to be used for accessing msg for printing/recording. Here cancel_stxn is the CANCEL transaction, though unlikely but still possible for a NIST. transaction_being_canceled is the Stx that is being canceled if this NIST is actually a CANCEL transaction itself. This will usually be set to an IST for CANCEL transactions. For all other non CANCEL transactions this will be nil. ok_to_send_481_to_cancel is a boolean that will be set from session when the conditions are there for 481/CANCEL to be sent. This will be the case when no STx is found on receiving CANCEL and both IST and NIST are in use.
msg_sent  [RW]  msg_sent is to be used for accessing msg for printing/recording. Here cancel_stxn is the CANCEL transaction, though unlikely but still possible for a NIST. transaction_being_canceled is the Stx that is being canceled if this NIST is actually a CANCEL transaction itself. This will usually be set to an IST for CANCEL transactions. For all other non CANCEL transactions this will be nil. ok_to_send_481_to_cancel is a boolean that will be set from session when the conditions are there for 481/CANCEL to be sent. This will be the case when no STx is found on receiving CANCEL and both IST and NIST are in use.
ok_to_send_481_to_cancel  [RW]  msg_sent is to be used for accessing msg for printing/recording. Here cancel_stxn is the CANCEL transaction, though unlikely but still possible for a NIST. transaction_being_canceled is the Stx that is being canceled if this NIST is actually a CANCEL transaction itself. This will usually be set to an IST for CANCEL transactions. For all other non CANCEL transactions this will be nil. ok_to_send_481_to_cancel is a boolean that will be set from session when the conditions are there for 481/CANCEL to be sent. This will be the case when no STx is found on receiving CANCEL and both IST and NIST are in use.
transaction_being_canceled  [RW]  msg_sent is to be used for accessing msg for printing/recording. Here cancel_stxn is the CANCEL transaction, though unlikely but still possible for a NIST. transaction_being_canceled is the Stx that is being canceled if this NIST is actually a CANCEL transaction itself. This will usually be set to an IST for CANCEL transactions. For all other non CANCEL transactions this will be nil. ok_to_send_481_to_cancel is a boolean that will be set from session when the conditions are there for 481/CANCEL to be sent. This will be the case when no STx is found on receiving CANCEL and both IST and NIST are in use.

Public Class methods

The transport to use, transport flags, remote ip and port the block is to be used to override the T1 and TimerJ etc. timer value. The block can for example have { self.t1 = 200; self.tj=100 } to override the T1, J on a transaction by transcation basis, otherwise the default is taken from SipperConfigurator or SIP::Transaction::BaseTransaction::T1 in that order. Usage: TU creates transaction and starts invoking "Invocation Action" methods. Also for requests received, checks whether to consume them or not based on consume? method return value. There are three call backs into TU from IST and they are notification on transport error and transaction timeout. There are 5 TU callbacks.

  (a) transaction_transport_err() gets called should IST get a transport failure
  (b) transaction_timeout() gets called on timeout of transaction
  (c) transaction_transaction_cleanup() gets called on transaction termination.
  (d) transaction_wrong_state() if the transaction transition is tried in a wrong state
      i.e a message is either received or being tried to send out in a state where it is
      illegal to do so.
  (e) transaction_record() record the message from the transaction.

Public Instance methods

RFC 3261 section 9.2 4th para last line A CANCEL request has no impact on the processing of transactions with any other method (other than INVITE) defined in this specification.

The NIST receives requests other than INVITE and ACK only

[Validate]