jsip
  1. jsip
  2. JSIP-311

Jain-sip stack does not repeat its response on the timeout of timer G, when INVITE transaction is in the completed state.

    Details

    • Type: Bug Bug
    • Status: Reopened
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: current
    • Fix Version/s: milestone 1
    • Component/s: www
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: PC

    • Issuezilla Id:
      311

      Description

      Make a call from caller to callee via sip proxy.
      callee responds 486 busy here, and proxy forwards it to the caller, but caller
      does not respond ACK.

      Expected:Proxy sip stack will repeat 486 response in T1, MIN(2*T1, T2), MIN
      (4*T1, T2).
      Actual:Proxy sip stack does not repeat 486 response.

        Activity

        Hide
        mranga added a comment -

        Proxy should not be doing this. The server transaction of the proxy is dead. The
        user agent (UAS) that issued 486 should retransmit the response.

        Show
        mranga added a comment - Proxy should not be doing this. The server transaction of the proxy is dead. The user agent (UAS) that issued 486 should retransmit the response.
        Hide
        mranga added a comment -

        Please provide a test case for this. Please state :

        • Version of jar file and date of your cvs version.
        Show
        mranga added a comment - Please provide a test case for this. Please state : Version of jar file and date of your cvs version.
        Hide
        mranga added a comment -

        There is a test case in the test suite that does check for this test. It does work.

        I think your response is being incorrectly generated - consequently the ACK is
        not being sent. You should attach more details such as a debug log and a test
        case before I can look at it.

        Show
        mranga added a comment - There is a test case in the test suite that does check for this test. It does work. I think your response is being incorrectly generated - consequently the ACK is not being sent. You should attach more details such as a debug log and a test case before I can look at it.
        Hide
        sophie0308 added a comment -

        When I opened this ticket in 2010-7-18, the jain-sip stack was using version
        1.2.150. Now the jain-sip stack is back using version 1.2.148, and the jain-sip
        stack can repeat 486 response very well.The bug can't be reproduced in version
        1.2.148.

        Show
        sophie0308 added a comment - When I opened this ticket in 2010-7-18, the jain-sip stack was using version 1.2.150. Now the jain-sip stack is back using version 1.2.148, and the jain-sip stack can repeat 486 response very well.The bug can't be reproduced in version 1.2.148.

          People

          • Assignee:
            jsip-issues
            Reporter:
            sophie0308
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: