sailfin
  1. sailfin
  2. SAILFIN-509

Test Agent. A real new request was not created if message window was not manually erased.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 1.0
    • Fix Version/s: milestone 1
    • Component/s: Tools
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      509

      Description

      NB, Test Agent 02/04/2008.

      To be able to start a really new request I manually erased the content of the
      message area and then pressed a button New Request. Otherwise the new request
      looks Ok, but for example, if after Register I've sent Invite without the
      cleaning the message window after Register request, then I've got 200 Ok as a
      response on Register, not Invite (see the bottom).

      I believe that New Request always has to generate a real new request.
      See also comments to the SAILFIN-383.

      INVITE

      NVITE sip:Alice@129.150.20.133 SIP/2.0
      From: "Alice" <sip:Alice@129.150.20.133>;tag=1202337422885
      To: "Alice" <sip:Alice@129.150.20.133>
      Max-Forwards: 70
      Content-Length: 11
      Cseq: 44 INVITE
      Contact: sip:129.150.20.133:6070;transport=UDP
      Content-Type: text/html
      Via: SIP/2.0/UDP 129.150.20.133:6070;branch=z9hG4bK-1202337411510
      Call-Id: 1202337422885

      200 OK response from Sailfin:

      SIP/2.0 200 OK
      From: "Alice" <sip:Alice@129.150.20.133>;tag=1202337411510
      To: "Alice" <sip:Alice@129.150.20.133>;tag=fccgrs7r-d
      Content-Length: 0
      Cseq: 43 REGISTER
      Contact: <sip:192.18.80.222:5060;fid=server_1>
      Server: Glassfish_SIP_1.0.0
      Via: SIP/2.0/UDP 129.150.20.133:6070;branch=z9hG4bK-1202337411510
      Call-Id: 1202337411510

        Activity

        Hide
        elnyvbo added a comment -

        added myself in cc

        Show
        elnyvbo added a comment - added myself in cc
        Hide
        vince kraemer added a comment -

        The label of the button that opens the editor has been made dynamic...

        If the "compose area" is empty, the text is 'New Request...'. If the "compose
        area" isn't empty, the label reads as 'Edit Current...'

        Show
        vince kraemer added a comment - The label of the button that opens the editor has been made dynamic... If the "compose area" is empty, the text is 'New Request...'. If the "compose area" isn't empty, the label reads as 'Edit Current...'
        Hide
        easarina added a comment -

        Build 02/15. I've opened Test Agent and sent a New Request (for example
        REGISTER). Then I've clicked at the button Edit Current. But I did not edit the
        request, just clicked Send. In this case 200 Ok that I've got, as a response
        on this request, had Call-id that corresponds to the previous REGISTER request.
        If to edit the request, then what kind of 200 OK will be received when this
        request will be sent, depends from how the request was edited. If was clicked
        enter, then will be a correct response, if enter was not clicked then can be
        different situations.
        The same will happen if to click at Edit Current, then don't edit, but Click OK
        and then click Send Message. Sometimes after that will be received a correct
        200, sometimes wrong.

        So basically it is unstable.

        REGISTER is most comfortable request to test this situation. INVITE will get
        very many 200, BYE will get 200 only if a proper session was created before
        (i.e. I've used INVITE, ACK, BYE (clicked BYE while I've selected 200, not ACK)).

        Show
        easarina added a comment - Build 02/15. I've opened Test Agent and sent a New Request (for example REGISTER). Then I've clicked at the button Edit Current. But I did not edit the request, just clicked Send. In this case 200 Ok that I've got, as a response on this request, had Call-id that corresponds to the previous REGISTER request. If to edit the request, then what kind of 200 OK will be received when this request will be sent, depends from how the request was edited. If was clicked enter, then will be a correct response, if enter was not clicked then can be different situations. The same will happen if to click at Edit Current, then don't edit, but Click OK and then click Send Message. Sometimes after that will be received a correct 200, sometimes wrong. So basically it is unstable. REGISTER is most comfortable request to test this situation. INVITE will get very many 200, BYE will get 200 only if a proper session was created before (i.e. I've used INVITE, ACK, BYE (clicked BYE while I've selected 200, not ACK)).
        Hide
        vince kraemer added a comment -

        If the user edits the current content of the buffer... they are responsible for
        adjusting things like the call ID... that is why it says 'Edit Current...' The
        test agent cannot read the users mind about what their intention is... They have
        to express that intention explicitly by editing the content of the request.

        A protocol level test agent should allow users to create incorrect requests...
        that is what makes it a test agent...

        Please reopen with detailed instructions on how to reproduce the situation that
        you are seeing, if you think this issue should be reopened.

        Show
        vince kraemer added a comment - If the user edits the current content of the buffer... they are responsible for adjusting things like the call ID... that is why it says 'Edit Current...' The test agent cannot read the users mind about what their intention is... They have to express that intention explicitly by editing the content of the request. A protocol level test agent should allow users to create incorrect requests... that is what makes it a test agent... Please reopen with detailed instructions on how to reproduce the situation that you are seeing, if you think this issue should be reopened.
        Hide
        easarina added a comment -

        I did not complain about many 200 OKs after INVITE.
        I did such steps:

        • Opened Test Agent, Clicked at New Request, sent REGISTER
          (clicked at the button Send)
        • Clicked Edit Current button
        • Did not change anything in the REGISTER request.
        • Clicked OK
        • Clicked Send Message
        • Checked in the history that in 200 OK response on this REGISTER
          I had a wrong Call-ID (from the previous REGISTER)

        Or such steps:

        • Opened Test Agent, Clicked at New Request, sent INVITE (clicked
          at the button Send)
        • Selected in the history 200 OK, sent ACK (the button on the
          right side, then Send Message)
        • Selected in the history 200 OK, clicked at the right side BYE,
          clicked Send Message
        • Clicked Eit Current (i.e BYE), did not edit, clickrf OK,
          clicked Send Message
        • 200 OK that will receive this BYE will have another call id
          (from the previous BYE).
        Show
        easarina added a comment - I did not complain about many 200 OKs after INVITE. I did such steps: Opened Test Agent, Clicked at New Request, sent REGISTER (clicked at the button Send) Clicked Edit Current button Did not change anything in the REGISTER request. Clicked OK Clicked Send Message Checked in the history that in 200 OK response on this REGISTER I had a wrong Call-ID (from the previous REGISTER) Or such steps: Opened Test Agent, Clicked at New Request, sent INVITE (clicked at the button Send) Selected in the history 200 OK, sent ACK (the button on the right side, then Send Message) Selected in the history 200 OK, clicked at the right side BYE, clicked Send Message Clicked Eit Current (i.e BYE), did not edit, clickrf OK, clicked Send Message 200 OK that will receive this BYE will have another call id (from the previous BYE).
        Hide
        easarina added a comment -

        Created an attachment (id=257)
        echo2 sip servlet

        Show
        easarina added a comment - Created an attachment (id=257) echo2 sip servlet
        Hide
        vince kraemer added a comment -

        another state machine issue...

        Show
        vince kraemer added a comment - another state machine issue...
        Show
        vince kraemer added a comment - http://fisheye5.cenqua.com/changelog/sailfin/tools/netbeans/testagent?cs=MAIN:vbkraemer:20080226010912

          People

          • Assignee:
            vince kraemer
            Reporter:
            easarina
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: