Details

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

      Operating System: All
      Platform: All

    • Issuezilla Id:
      3

      Description

      In the existing NIST implementation, receive() in
      SipClientConnectionImpl always updates the received response with
      the latest one. It means that whenever application does receive(),it
      always receives the most recent (latest) response. Is it an expected
      behaviour? For example, if an application sends INVITE and server
      sends 100, 180 and 200, the application might see only 200 and won't
      be aware that it had also received 100 and 180 responses. Probably,
      it does not matter if we lose any provisional responses and receive
      only the final; but it would matter if we also lose any final
      "intermediate" responses as SipClientConnectionImpl does not queue
      up any responses. Would it be a bug in SipClientConnectionImpl?

      >Yes it is a bug

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            sip-for-me-issues
            Reporter:
            deruelle_jean
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated: