[OpenSIPS-Users] YNT: Re: YNT: Re: YNT: Re: RFC3261 transaction matching failed error for the second 401 Unauthorized - Challenging the UE

Kaan Dandin kaandandin at yahoo.com
Thu Oct 16 18:35:32 CEST 2014


Hi Bogdan,

Thanks for your support.
All of the messages until inbound ACK to OpenSIPS have  record route header. 
Inbound ACK is having only truncated route information. 
It seems that IMS bench is not putting  Record Route header to ACK although is it is configured like following.


related part of ims bench ims_uac.xml script
==================================

  <!-- By adding rrs="true" (Record Route Sets), the route sets are -->
  <!-- saved and used for following messages sent.                  -->
  <recv response="200" rrs="true">
  </recv>

  <send>
    <![CDATA[

      ACK [next_url] SIP/2.0
      [last_Via:]
      Max-Forwards: 70
      [routes:]
      From: "[field0]" <sip:[field0]@[field1]>;tag=[pid]SIPpTag00[call_number]
      [last_To:]
      Call-ID: [call_id]
      CSeq: 1 ACK
      Content-Length: 0

    ]]>
  </send>


200 OK coming to OpenSIPS
===============================

Internet Protocol, Src: 192.168.2.3 (192.168.2.3), Dst: 192.168.2.141 (192.168.2.141)
    Version: 4
    Source: 192.168.2.3 (192.168.2.3)
    Destination: 192.168.2.141 (192.168.2.141)
User Datagram Protocol, Src Port: dsmeter_iatc (4060), Dst Port: dsmeter_iatc (4060)
    Source port: dsmeter_iatc (4060)
    Destination port: dsmeter_iatc (4060)
    Length: 1017
    Checksum: 0x822b [correct]
Session Initiation Protocol
    Status-Line: SIP/2.0 200 OK
        Status-Code: 200
        [Resent Packet: False]
    Message Header
        Via: SIP/2.0/UDP 192.168.2.141:4060;received=192.168.2.141;rport=4060;branch=z9hG4bK8c0f.49ecef52.0
            Transport: UDP
            Sent-by Address: 192.168.2.141
            Sent-by port: 4060
            Received: 192.168.2.141
            RPort: 4060
            Branch: z9hG4bK8c0f.49ecef52.0
        Via: SIP/2.0/UDP 192.168.2.11:9048;branch=z9hG4bK-3672-12-4
            Transport: UDP
            Sent-by Address: 192.168.2.11
            Sent-by port: 9048
            Branch: z9hG4bK-3672-12-4
        Record-Route: <sip:192.168.2.141;lr;ftag=3672SIPpTag0012>
        Record-Route: <sip:mt at pcscf.open-ims.test:4060;lr>
        Record-Route: <sip:mt at scscf.open-ims.test:6060;lr>
        Record-Route: <sip:mo at scscf.open-ims.test:6060;lr>
        Record-Route: <sip:mo at pcscf.open-ims.test:4060;lr>
        Record-Route: <sip:192.168.2.141;lr;ftag=3672SIPpTag0012>
        


200 OK from OpenSIPS to IMS bench
===============================

   2254 32.327316   192.168.2.141         192.168.2.11          SIP/SDP  Status: 200 OK, with session description

Frame 2254 (950 bytes on wire, 950 bytes captured)
Ethernet II, Src: Vmware_22:e0:4c (00:0c:29:22:e0:4c), Dst: Vmware_d2:6a:2a (00:0c:29:d2:6a:2a)
Internet Protocol, Src: 192.168.2.141 (192.168.2.141), Dst: 192.168.2.11 (192.168.2.11)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x10 (DSCP 0x04: Unknown DSCP; ECN: 0x00)
    Total Length: 936
    Identification: 0x2277 (8823)
    Flags: 0x04 (Don't Fragment)
    Fragment offset: 0
    Time to live: 64
    Protocol: UDP (0x11)
    Header checksum: 0x8ed5 [correct]
    Source: 192.168.2.141 (192.168.2.141)
    Destination: 192.168.2.11 (192.168.2.11)
User Datagram Protocol, Src Port: dsmeter_iatc (4060), Dst Port: 9048 (9048)
    Source port: dsmeter_iatc (4060)
    Destination port: 9048 (9048)
    Length: 916
    Checksum: 0xed25 [correct]
Session Initiation Protocol
    Status-Line: SIP/2.0 200 OK
        Status-Code: 200
        [Resent Packet: False]
    Message Header
        Via: SIP/2.0/UDP 192.168.2.11:9048;branch=z9hG4bK-3672-12-4
            Transport: UDP
            Sent-by Address: 192.168.2.11
            Sent-by port: 9048
            Branch: z9hG4bK-3672-12-4
        Record-Route: <sip:192.168.2.141;lr;ftag=3672SIPpTag0012>
        Record-Route: <sip:mt at pcscf.open-ims.test:4060;lr>
        Record-Route: <sip:mt at scscf.open-ims.test:6060;lr>
        Record-Route: <sip:mo at scscf.open-ims.test:6060;lr>
        Record-Route: <sip:mo at pcscf.open-ims.test:4060;lr>
        Record-Route: <sip:192.168.2.141;lr;ftag=3672SIPpTag0012>


ACK from IMS bench to OpenSIPS
=====================


No.     Time        Source                Destination           Protocol Info
   2255 32.328365   192.168.2.11          192.168.2.141         SIP      Request: ACK sip:subs002590 at 192.168.2.11:9590;transport=UDP

Frame 2255 (635 bytes on wire, 635 bytes captured)
Ethernet II, Src: Vmware_d2:6a:2a (00:0c:29:d2:6a:2a), Dst: Vmware_22:e0:4c (00:0c:29:22:e0:4c)
Internet Protocol, Src: 192.168.2.11 (192.168.2.11), Dst: 192.168.2.141 (192.168.2.141)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
    Total Length: 621
    Identification: 0x5204 (20996)
    Flags: 0x04 (Don't Fragment)
    Fragment offset: 0
    Time to live: 64
    Protocol: UDP (0x11)
    Header checksum: 0x6093 [correct]
    Source: 192.168.2.11 (192.168.2.11)
    Destination: 192.168.2.141 (192.168.2.141)
User Datagram Protocol, Src Port: 9048 (9048), Dst Port: dsmeter_iatc (4060)
    Source port: 9048 (9048)
    Destination port: dsmeter_iatc (4060)
    Length: 601
    Checksum: 0x3460 [correct]
Session Initiation Protocol
    Request-Line: ACK sip:subs002590 at 192.168.2.11:9590;transport=UDP SIP/2.0
        Method: ACK
        [Resent Packet: False]
    Message Header
        Via: SIP/2.0/UDP 192.168.2.11:9048;branch=z9hG4bK-3672-12-4
            Transport: UDP
            Sent-by Address: 192.168.2.11
            Sent-by port: 9048
            Branch: z9hG4bK-3672-12-4
        Max-Forwards: 70
        [truncated] Route:  <sip:192.168.2.141;lr;ftag=3672SIPpTag0012>, <sip:mo at pcscf.open-ims.test:4060;lr>, <sip:mo at scscf.open-ims.test:6060;lr>, <sip:mt at scscf.open-ims.test:6060;lr>, <sip:mt at pcscf.open-ims.test:4060;lr>,<sip:192.168.2.141;lr;f
        From: "subs002048" <sip:subs002048 at open-ims.test>;tag=3672SIPpTag0012
            SIP Display info: "subs002048" 
            SIP from address: sip:subs002048 at open-ims.test
            SIP tag: 3672SIPpTag0012
        To: "subs002590" <sip:subs002590 at open-ims.test>;tag=3672SIPpTag0113
            SIP Display info: "subs002590" 
            SIP to address: sip:subs002590 at open-ims.test
            SIP tag: 3672SIPpTag0113
        Call-ID: 12-3672 at 192.168.2.11
        CSeq: 1 ACK
            Sequence Number: 1
            Method: ACK
        Content-Length: 0

ACK forwarded to wrong destination
==============================

No.     Time        Source                Destination           Protocol Info
   2256 32.333313   192.168.2.141         192.168.2.5           SIP      Request: ACK sip:subs002590 at 192.168.2.11:9590;transport=UDP

Frame 2256 (716 bytes on wire, 716 bytes captured)
Ethernet II, Src: Vmware_22:e0:4c (00:0c:29:22:e0:4c), Dst: Vmware_0d:bf:1f (00:0c:29:0d:bf:1f)
Internet Protocol, Src: 192.168.2.141 (192.168.2.141), Dst: 192.168.2.5 (192.168.2.5)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x10 (DSCP 0x04: Unknown DSCP; ECN: 0x00)
    Total Length: 702
    Identification: 0xf0d8 (61656)
    Flags: 0x04 (Don't Fragment)
    Fragment offset: 0
    Time to live: 64
    Protocol: UDP (0x11)
    Header checksum: 0xc163 [correct]
    Source: 192.168.2.141 (192.168.2.141)
    Destination: 192.168.2.5 (192.168.2.5)
User Datagram Protocol, Src Port: dsmeter_iatc (4060), Dst Port: dsmeter_iatc (4060)
    Source port: dsmeter_iatc (4060)
    Destination port: dsmeter_iatc (4060)
    Length: 682
    Checksum: 0x0f4e [correct]
Session Initiation Protocol
    Request-Line: ACK sip:subs002590 at 192.168.2.11:9590;transport=UDP SIP/2.0
        Method: ACK
        [Resent Packet: False]
    Message Header
        Record-Route: <sip:192.168.2.141;lr;ftag=3672SIPpTag0012>
        Via: SIP/2.0/UDP 192.168.2.141:4060;branch=z9hG4bK8c0f.49ecef52.2
            Transport: UDP
            Sent-by Address: 192.168.2.141
            Sent-by port: 4060
            Branch: z9hG4bK8c0f.49ecef52.2
        Via: SIP/2.0/UDP 192.168.2.11:9048;branch=z9hG4bK-3672-12-4
            Transport: UDP
            Sent-by Address: 192.168.2.11
            Sent-by port: 9048
            Branch: z9hG4bK-3672-12-4
        Max-Forwards: 70
        Route:  <sip:mo at pcscf.open-ims.test:4060;lr>, <sip:mo at scscf.open-ims.test:6060;lr>, <sip:mt at scscf.open-ims.test:6060;lr>, <sip:mt at pcscf.open-ims.test:4060;lr>,<sip:192.168.2.141;lr;ftag=3672SIPpTag0012>
        From: "subs002048" <sip:subs002048 at open-ims.test>;tag=3672SIPpTag0012
            SIP Display info: "subs002048" 
            SIP from address: sip:subs002048 at open-ims.test
            SIP tag: 3672SIPpTag0012
        To: "subs002590" <sip:subs002590 at open-ims.test>;tag=3672SIPpTag0113
            SIP Display info: "subs002590" 
            SIP to address: sip:subs002590 at open-ims.test
            SIP tag: 3672SIPpTag0113
        Call-ID: 12-3672 at 192.168.2.11
        CSeq: 1 ACK
            Sequence Number: 1
            Method: ACK
        Content-Length: 0


Kind regards,
Kaan


________________________________
 From: Bogdan-Andrei Iancu <bogdan at opensips.org>
To: Kaan Dandin <kaandandin at yahoo.com>; OpenSIPS users mailling list <users at lists.opensips.org> 
Cc: Gunes Kurt <gkurt at itu.edu.tr>; "Ibrahim Hokelek, (BİLGEM-UEKAE)" <ibrahim.hokelek at tubitak.gov.tr> 
Sent: Thursday, October 16, 2014 10:01 AM
Subject: Re: YNT: Re: YNT: Re: YNT: Re: [OpenSIPS-Users] RFC3261 transaction matching failed error for the second 401 Unauthorized - Challenging the UE
 


Hi Kaan,

What you need to check is : do the ACK and BYE you receive in
        OpenSIPS have a Route hdr ? So, :
    check if the outbound INVITE (leaving OpenSIPS) has a Record-Route
        hdr
    check if the incoming 200 OK to INVITE (from UAS) has a
        Record-Route hdr
    check in inbound ACK (from UAC to OpenSIPS) has a Route hdr. 

Let me know.

REgards,
 
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer http://www.opensips-solutions.com
On 16.10.2014 00:25, Kaan Dandin wrote:

Hi Bogdan,
>
>
>Thanks for your response. I have check the related documentation once more.
>But it in fact, I was already using record_route and loose_route.
>
>
>When I receive initial INVITE I use record_route.
>
>
>When the following messages has to_tag , I am checking with loose_route and making the routing with t_relay.
>
>
>This is working properly for the messages before ACK and BYE.
>
>
>But for ACK and  BYE messages it is not able to find route and  making a DNS lookup  and since
>pcscf.open-ims.test is configured as 192.168.2.5 , it is always going to .5 openims node.
>
>
>The difference between 180 Ringing , 200 OK which is passed properly and ACK and BYE messages seems Via headers. 180 Ringing has all the via headers.
>
>
>related part of script for record_route()
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20141016/c95114c9/attachment-0001.htm>


More information about the Users mailing list