search

cdotsip / jain-sip

Automatically exported from code.google.com/p/jain-sip
0 stars 1 forks source link

Timeout timer shouldn't be stopped on a 100 trying #46

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. client sends an INVITE
2. server sends a 100 trying
3. server never sends an INVITE response
4. client never times out the INVITE

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

SIPClientTransactionImpl.inviteClientTransaction() line 841 should be removed:

      } else if (statusCode / 100 == 1) {
        disableRetransmissionTimer();
//        disableTimeoutTimer();
        this.setState(TransactionState._PROCEEDING);

        if (respondTo != null)
          respondTo.processResponse(transactionResponse, encapsulatedChannel, dialog);
        else {
          this.semRelease();
        }

      }

Original issue reported on code.google.com by ericfpig...@gmail.com on 17 Jan 2013 at 6:52

GoogleCodeExporter commented 9 years ago

Original comment by laurent....@gmail.com on 24 Jan 2013 at 1:27

GoogleCodeExporter commented 9 years ago

Original comment by laurent....@gmail.com on 24 Jan 2013 at 1:34

GoogleCodeExporter commented 9 years ago 
Please check Section 17.1.1.2 of RFC3261, the state machine shows that if this 
happens the CTX is not timed out as there is no timers to time it out. To this 
effect you can use gov.nist.javax.sip.MAX_TX_LIFETIME_NON_INVITE and 
gov.nist.javax.sip.MAX_TX_LIFETIME_INVITE properties in the sip stack 
properties, you can check the full list here 
https://mobicents.ci.cloudbees.com/job/JAIN-SIP/lastSuccessfulBuild/artifact/jai
n-sip/javadoc/index.html

Marking as Invalid. PLease comment if you think that the issue is still valid

Original comment by jean.deruelle on 19 Mar 2013 at 5:14