sailfin
  1. sailfin
  2. SAILFIN-1337

NB, SIP Test Agent. Can not send not default request.

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.0
    • Fix Version/s: milestone 1
    • Component/s: Tools
    • Labels:
      None
    • Environment:

      Operating System: Solaris SPARC
      Platform: All

    • Issuezilla Id:
      1,337
    • Tags:

      Description

      I've installed on the same Solaris 10 Sparc machine NB 6.1 and Sailfin b57 (DAS).

      I've deployed to Sailfin presence archive and run publish scenario, see
      as-telco-sqe/stress-ws/presence.

      I've sent just one publish message using sipp. In the sipp log I had two
      messages, a Publish message from sipp and 200 response from Sailfin:
      ======================================================================
      ----------------------------------------------- 2008-10-30 10:47:47:907.119
      TCP message sent (658 bytes):

      PUBLISH sip:abc@eas.al.sw.ericsson.se SIP/2.0
      Via: SIP/2.0/TCP 10.5.79.227:5091;branch=z9hG4bK-10184-1-0
      From: sip:sipp@10.5.79.227:5091;tag=1
      To: sip:abc@eas.al.sw.ericsson.se
      Call-ID: 1-10184@10.5.79.227
      CSeq: 1 PUBLISH
      Expires: 3600
      Max-Forwards: 70
      User-Agent: sipp
      Event: presence
      Content-Type: application/cpim-pidf+xml
      Content-Length: 296

      <?xml version="1.0" encoding="UTF-8"?>
      <presence xmlns="urn:ietf:params:xml:ns:pidf"
      xmlns:pcap="urn:poc:params:xml:pidf-pcap"
      entity="sip:alice@ericsson.com">
      <tuple id="123">
      <status>
      <basic>open</basic>
      <pcap:capability name="PoC">open</pcap:capability>
      </status>
      </tuple>
      </presence>
      ----------------------------------------------- 2008-10-30 10:47:48:278.645
      TCP message received [281] bytes :

      SIP/2.0 200 OK
      Content-Length: 0
      To: <sip:abc@eas.al.sw.ericsson.se>;tag=fmxolm24-1
      Expires: 3600
      Cseq: 1 PUBLISH
      Via: SIP/2.0/TCP 10.5.79.227:5091;branch=z9hG4bK-10184-1-0
      Call-Id: 1-10184@10.5.79.227
      From: <sip:sipp@10.5.79.227:5091>;tag=1
      Server: Glassfish_SIP_1.0.0
      ===============================================================

      So using NB test agent I've tried to send exactly this PUBLISH message:
      ======================================================
      PUBLISH sip:abc@eas.al.sw.ericsson.se SIP/2.0
      Via: SIP/2.0/TCP 10.5.79.227:5091;branch=z9hG4bK-10184-1-0
      From: sip:sipp@10.5.79.227:5091;tag=1
      To: sip:abc@eas.al.sw.ericsson.se
      Call-ID: 1-10184@10.5.79.227
      CSeq: 1 PUBLISH
      Expires: 3600
      Max-Forwards: 70
      User-Agent: sipp
      Event: presence
      Content-Type: application/cpim-pidf+xml
      Content-Length: 296
      ===================================================================
      I did so changing the default values and adding and removing some fields.

      When I've sent this PUBLISH request, then under "Message Creation" I saw:
      ===============================================
      PUBLISH SIP/2.0
      From: "Alice" <>;tag=1225389424031
      To: "Alice" <>
      Max-Forwards: 70
      Content-Length: 296
      Expires: 3600
      User-Agent: sipp
      Cseq: 1 PUBLISH
      Event: presence
      Content-Type: application/cpim-pidf+xmll
      Via: sipp
      Call-Id: 1-10184@10.5.79.227
      ============================================

      So in this request Via, To, From, and the line after Publish had wrong values,
      not the values that I've put there.

      But at the Message History I saw that was just sent a default REGISTER request,
      that I did not send at all:
      ======================================================
      REGISTER sip:Alice@192.18.80.222 SIP/2.0
      From: "Alice" <sip:Alice@192.18.80.222>;tag=1225389865661
      To: "Alice" <sip:Alice@192.18.80.222>
      Max-Forwards: 70
      Content-Length: 11
      Cseq: 4 REGISTER
      Contact: sip:192.18.80.222:6062;transport=UDP
      Content-Type: text/html
      Via: SIP/2.0/UDP 192.18.80.222:6062;branch=z9hG4bK-1225389865659
      Call-Id: 1225389865661

      Hello World
      =========================================================

      I've closed the SIP Test Agent, opened it again and tried to send the same
      Publish request again, but I got the same problems.

      But when I've tried to send just default Publish requests, it was OK.

        Activity

        Hide
        easarina added a comment -

        The same problem happened with INVITE request:
        I wanted to send:

        INVITE sip:service@192.18.80.222:5060;transport=TCP SIP/2.0
        Via: SIP/2.0/TCP 192.18.80.222:6066;branch=z9hG4bK-21215-1-0
        From: sipp <sip:sipp@192.18.80.222:6066>;tag=21215SIPpTag001
        To: sut <sip:service@192.18.80.222:5060>
        Call-ID: 1-21215@10.5.220.18
        CSeq: 1 INVITE
        Contact: <sip:sipp@192.18.80.222:6066;transport=TCP>
        Max-Forwards: 70
        Subject: InviteProxy Performance Test
        Test-Type: uas
        Content-Type: application/sdp
        Content-Length: 131

        v=0
        o=user1 53655765 2353687637 IN IP4 10.5.220.18
        s=-
        c=IN IP4 10.5.220.18
        t=0 0
        m=audio 6009 RTP/AVP 0
        a=rtpmap:0 PCMU/8000

        In Message Creation I saw:

        NVITE sip:service@192.18.80.222:5060;transport=TCP SIP/2.0 SIP/2.0
        From: "Alice" <sipp
        <sip:sipp@192.18.80.222:6066>;tag=21215SIPpTag001>;tag=1225396843065
        To: "Alice" <sut <sip:service@192.18.80.222:5060>>
        Content-Length: 131
        Max-Forwards: 70
        Cseq: 1 INVITE
        Contact: <sip:sipp@192.18.80.222:6066;transport=TCP>
        Subject: InviteProxy Performance Test
        Content-Type: application/sdp
        Call-Id: 1-21215@10.5.220.18
        Via: SIP/2.0/UDP 192.18.80.222:6066;branch=z9hG4bK-1225396843064

        v=0
        o=user1 53655765 2353687637 IN IP4 10.5.220.18
        s=-
        c=IN IP4 10.5.220.18
        t=0 0
        m=audio 6009 RTP/AVP 0
        a=rtpmap:0 PCMU/8000

        But then anyway was sent a default REGISTER request.

        When I've tried to send INVITE again removing Name Alice (I've restarted SIP
        Test Agent). The request in Message Creation alrady had wrong values.

        Show
        easarina added a comment - The same problem happened with INVITE request: I wanted to send: INVITE sip:service@192.18.80.222:5060;transport=TCP SIP/2.0 Via: SIP/2.0/TCP 192.18.80.222:6066;branch=z9hG4bK-21215-1-0 From: sipp <sip:sipp@192.18.80.222:6066>;tag=21215SIPpTag001 To: sut <sip:service@192.18.80.222:5060> Call-ID: 1-21215@10.5.220.18 CSeq: 1 INVITE Contact: <sip:sipp@192.18.80.222:6066;transport=TCP> Max-Forwards: 70 Subject: InviteProxy Performance Test Test-Type: uas Content-Type: application/sdp Content-Length: 131 v=0 o=user1 53655765 2353687637 IN IP4 10.5.220.18 s=- c=IN IP4 10.5.220.18 t=0 0 m=audio 6009 RTP/AVP 0 a=rtpmap:0 PCMU/8000 In Message Creation I saw: NVITE sip:service@192.18.80.222:5060;transport=TCP SIP/2.0 SIP/2.0 From: "Alice" <sipp <sip:sipp@192.18.80.222:6066>;tag=21215SIPpTag001>;tag=1225396843065 To: "Alice" <sut <sip:service@192.18.80.222:5060>> Content-Length: 131 Max-Forwards: 70 Cseq: 1 INVITE Contact: <sip:sipp@192.18.80.222:6066;transport=TCP> Subject: InviteProxy Performance Test Content-Type: application/sdp Call-Id: 1-21215@10.5.220.18 Via: SIP/2.0/UDP 192.18.80.222:6066;branch=z9hG4bK-1225396843064 v=0 o=user1 53655765 2353687637 IN IP4 10.5.220.18 s=- c=IN IP4 10.5.220.18 t=0 0 m=audio 6009 RTP/AVP 0 a=rtpmap:0 PCMU/8000 But then anyway was sent a default REGISTER request. When I've tried to send INVITE again removing Name Alice (I've restarted SIP Test Agent). The request in Message Creation alrady had wrong values.
        Hide
        vince kraemer added a comment -

        a failing validation of CallID causes the data the user entered to be ignored
        and a new 'default' request to get sent..

        Show
        vince kraemer added a comment - a failing validation of CallID causes the data the user entered to be ignored and a new 'default' request to get sent..
        Show
        vince kraemer added a comment - http://fisheye5.cenqua.com/changelog/sailfin/?cs=MAIN:vbkraemer:20081103230004
        Hide
        easarina added a comment -

        Sailfin promoted b60f, NB 6.5, x86 machines.

        I don't think that this bug was fixed.
        I've used TCP in my tests.
        1) I've created adefault publish request. Only in URL line I put
        sip:abc@eas.al.sw.ericsson.se

        Then I've removed a value from Call-id field.

        I saw such request in Message Creation window:
        ===========================================================
        PUBLISH sip:abc@eas.al.sw.ericsson.se SIP/2.0
        From: "Alice" <sip:Alice@10.5.217.32>;tag=1231448701773
        To: "Alice" <sip:Alice@10.5.217.32>
        Max-Forwards: 70
        Content-Length: 11
        Contact: sip:10.5.217.32:6060;transport=TCP
        Cseq: 42 PUBLISH
        Via: SIP/2.0/TCP 10.5.217.32:6060;branch=z9hG4bK-1231448701772
        Content-Type: text/html
        Call-Id:
        Hello World
        ================================================
        But really was sent such REGISTER request( from Message Historry window):
        +++++++++++++++++++++++++++++++++++++++++++++++++++
        REGISTER sip:Alice@10.5.217.32 SIP/2.0
        From: "Alice" <sip:Alice@10.5.217.32>;tag=1231447136252
        To: "Alice" <sip:Alice@10.5.217.32>
        Max-Forwards: 70
        Content-Length: 11
        Contact: sip:10.5.217.32:6060;transport=TCP
        Cseq: 2 REGISTER
        Via: SIP/2.0/TCP 10.5.217.32:6060;branch=z9hG4bK-1231447136251
        Content-Type: text/html
        Call-Id: 1231447136252

        Hello World
        +++++++++++++++++++++++++++++++++++++++++++++

        I've created again a default PUBLISH request and made the experiment with URL
        field. In URL fiesld I put: sip:abc@eas.al.sw.ericsson.se SIP/2.0

        As a result was created such request (from Message Creation):
        ===========================================================
        PUBLISH sip:abc@eas.al.sw.ericsson.se SIP/2.0 SIP/2.0
        From: "Alice" <sip:Alice@10.5.217.32>;tag=1231448321193
        To: "Alise" <sip:Alice@10.5.217.32>
        Max-Forwards: 70
        Content-Length: 11
        Contact: sip:10.5.217.32:6060;transport=TCP
        Cseq: 42 PUBLISH
        Via: SIP/2.0/TCP 10.5.217.32:6060;branch=z9hG4bK-1231448321192
        Content-Type: text/html
        Call-Id: 1231448321193

        Hello World
        ===========================================

        But really was sent such request (from Message History)

        +++++++++++++++++++++++++++++++++++++++++++++++++

        REGISTER sip:Alice@10.5.217.32 SIP/2.0
        From: "Alice" <sip:Alice@10.5.217.32>;tag=1231447136252
        To: "Alice" <sip:Alice@10.5.217.32>
        Max-Forwards: 70
        Content-Length: 11
        Contact: sip:10.5.217.32:6060;transport=TCP
        Cseq: 2 REGISTER
        Via: SIP/2.0/TCP 10.5.217.32:6060;branch=z9hG4bK-1231447136251
        Content-Type: text/html
        Call-Id: 1231447136252

        Hello World
        ++++++++++++++++++++++++++++++++++++++++

        And I saw that Register request was sent in other cases of a wrong formats also.
        For example, two Call-id fields. I believe that in all such cases have to be
        seen a wrong format error message, but not a default Register request.

        Show
        easarina added a comment - Sailfin promoted b60f, NB 6.5, x86 machines. I don't think that this bug was fixed. I've used TCP in my tests. 1) I've created adefault publish request. Only in URL line I put sip:abc@eas.al.sw.ericsson.se Then I've removed a value from Call-id field. I saw such request in Message Creation window: =========================================================== PUBLISH sip:abc@eas.al.sw.ericsson.se SIP/2.0 From: "Alice" <sip:Alice@10.5.217.32>;tag=1231448701773 To: "Alice" <sip:Alice@10.5.217.32> Max-Forwards: 70 Content-Length: 11 Contact: sip:10.5.217.32:6060;transport=TCP Cseq: 42 PUBLISH Via: SIP/2.0/TCP 10.5.217.32:6060;branch=z9hG4bK-1231448701772 Content-Type: text/html Call-Id: Hello World ================================================ But really was sent such REGISTER request( from Message Historry window): +++++++++++++++++++++++++++++++++++++++++++++++++++ REGISTER sip:Alice@10.5.217.32 SIP/2.0 From: "Alice" <sip:Alice@10.5.217.32>;tag=1231447136252 To: "Alice" <sip:Alice@10.5.217.32> Max-Forwards: 70 Content-Length: 11 Contact: sip:10.5.217.32:6060;transport=TCP Cseq: 2 REGISTER Via: SIP/2.0/TCP 10.5.217.32:6060;branch=z9hG4bK-1231447136251 Content-Type: text/html Call-Id: 1231447136252 Hello World +++++++++++++++++++++++++++++++++++++++++++++ I've created again a default PUBLISH request and made the experiment with URL field. In URL fiesld I put: sip:abc@eas.al.sw.ericsson.se SIP/2.0 As a result was created such request (from Message Creation): =========================================================== PUBLISH sip:abc@eas.al.sw.ericsson.se SIP/2.0 SIP/2.0 From: "Alice" <sip:Alice@10.5.217.32>;tag=1231448321193 To: "Alise" <sip:Alice@10.5.217.32> Max-Forwards: 70 Content-Length: 11 Contact: sip:10.5.217.32:6060;transport=TCP Cseq: 42 PUBLISH Via: SIP/2.0/TCP 10.5.217.32:6060;branch=z9hG4bK-1231448321192 Content-Type: text/html Call-Id: 1231448321193 Hello World =========================================== But really was sent such request (from Message History) +++++++++++++++++++++++++++++++++++++++++++++++++ REGISTER sip:Alice@10.5.217.32 SIP/2.0 From: "Alice" <sip:Alice@10.5.217.32>;tag=1231447136252 To: "Alice" <sip:Alice@10.5.217.32> Max-Forwards: 70 Content-Length: 11 Contact: sip:10.5.217.32:6060;transport=TCP Cseq: 2 REGISTER Via: SIP/2.0/TCP 10.5.217.32:6060;branch=z9hG4bK-1231447136251 Content-Type: text/html Call-Id: 1231447136252 Hello World ++++++++++++++++++++++++++++++++++++++++ And I saw that Register request was sent in other cases of a wrong formats also. For example, two Call-id fields. I believe that in all such cases have to be seen a wrong format error message, but not a default Register request.
        Hide
        prasads added a comment -

        "Reclassifying as P4 because these issues are not must fix for SailFin 1.0 release.
        This issue will be scrubbed after this release and will be given the right
        priority for SailFin 2.0 release."

        Show
        prasads added a comment - "Reclassifying as P4 because these issues are not must fix for SailFin 1.0 release. This issue will be scrubbed after this release and will be given the right priority for SailFin 2.0 release."
        Hide
        prasads added a comment -

        Resetting the priority back to the original one.

        Show
        prasads added a comment - Resetting the priority back to the original one.
        Hide
        prasads added a comment -

        Downgrading to a P4

        Show
        prasads added a comment - Downgrading to a P4

          People

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

            Dates

            • Created:
              Updated: