[sr-dev] problem with locally generated ACKs

[Daniel-Constantin Mierla]

On 12/17/09 2:59 PM, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>   >  ack and cancel are generated by other part of tm, where event_route is
>   >  not executed. However, afaik, tm should automatically send the such ack
>   >  and cancel where the invite was sent.
>
> daniel,
>
> thanks for your response.  see wireshark output below.  ack is NOT sent
> to the same ip/port as invite.
>    

I see, i will try to look over the code later today or maybe Andrei can 
give a faster answer meanwhile.

Cheers,
Daniel

> -- juha
>
> ------------------------------------------------------------------------
>
> No.     Time            Source                Destination           Protocol Info
>        4 15:48:23.012034 192.98.101.10         192.98.101.132        SIP/SDP  Request: INVITE sip:jh_tutpro_com at 192.168.0.169:5074;transport=udp, with session description
>
> Frame 4 (624 bytes on wire, 624 bytes captured)
> Linux cooked capture
> Internet Protocol, Src: 192.98.101.10 (192.98.101.10), Dst: 192.98.101.132 (192.98.101.132)
> User Datagram Protocol, Src Port: sip (5060), Dst Port: 60705 (60705)
> Session Initiation Protocol
>      Request-Line: INVITE sip:jh_tutpro_com at 192.168.0.169:5074;transport=udp SIP/2.0
>      Message Header
>          Via: SIP/2.0/UDP 192.98.101.10;branch=z9hG4bKfb.dfd399d1.0
>          To:<sip:jh at tutpro.com>
>          From:<sip:click2dial at tutpro.com>;tag=4b2a36a70277f
>          CSeq: 1 INVITE
>          Call-ID: 4b2a36a70277f at tutpro.com
>          Content-Length: 131
>          User-Agent: SIP Proxy  (2.99.99-pre3 (i386/linux))
>          Contact:<sip:click2dial at 192.98.101.10:5060>
>          Reject-Contact: *;automata="YES"
>          Content-Type: application/sdp
>      Message Body
>          Session Description Protocol
>              Session Description Protocol Version (v): 0
>              Owner/Creator, Session Id (o): click-to-dial 0 0 IN IP4 0.0.0.0
>              Session Name (s): session
>              Connection Information (c): IN IP4 0.0.0.0
>              Bandwidth Information (b): CT:1000
>              Time Description, active time (t): 0 0
>              Media Description, name and address (m): audio 9 RTP/AVP 0
>              Media Attribute (a): rtpmap:0 PCMU/8000
>
> No.     Time            Source                Destination           Protocol Info
>        8 15:48:25.439877 192.98.101.132        192.98.101.10         SIP/SDP  Status: 200 OK, with session description
>
> Frame 8 (719 bytes on wire, 719 bytes captured)
> Linux cooked capture
> Internet Protocol, Src: 192.98.101.132 (192.98.101.132), Dst: 192.98.101.10 (192.98.101.10)
> User Datagram Protocol, Src Port: 60705 (60705), Dst Port: sip (5060)
> Session Initiation Protocol
>      Status-Line: SIP/2.0 200 OK
>      Message Header
>          Via: SIP/2.0/UDP 192.98.101.10;branch=z9hG4bKfb.dfd399d1.0
>          To:<sip:jh at tutpro.com>;tag=qpgxk
>          From:<sip:click2dial at tutpro.com>;tag=4b2a36a70277f
>          Call-ID: 4b2a36a70277f at tutpro.com
>          CSeq: 1 INVITE
>          Contact:<sip:jh_tutpro_com at 192.168.0.169:5074;transport=udp>
>          Content-Type: application/sdp
>          Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE
>          Server: Twinkle/1.3.2
>          Supported: replaces,norefersub
>          Content-Length: 208
>      Message Body
>          Session Description Protocol
>              Session Description Protocol Version (v): 0
>              Owner/Creator, Session Id (o): twinkle 1232785010 225740651 IN IP4 192.168.0.169
>              Session Name (s): -
>              Connection Information (c): IN IP4 192.168.0.169
>              Time Description, active time (t): 0 0
>              Media Description, name and address (m): audio 8000 RTP/AVP 0 101
>              Media Attribute (a): rtpmap:0 PCMU/8000
>              Media Attribute (a): rtpmap:101 telephone-event/8000
>              Media Attribute (a): fmtp:101 0-15
>              Media Attribute (a): ptime:20
>
> No.     Time            Source                Destination           Protocol Info
>        9 15:48:25.440175 192.98.101.10         192.168.0.169         SIP      Request: ACK sip:jh_tutpro_com at 192.168.0.169:5074;transport=udp
>
> Frame 9 (384 bytes on wire, 384 bytes captured)
> Linux cooked capture
> Internet Protocol, Src: 192.98.101.10 (192.98.101.10), Dst: 192.168.0.169 (192.168.0.169)
> User Datagram Protocol, Src Port: sip (5060), Dst Port: alesquery (5074)
> Session Initiation Protocol
>      Request-Line: ACK sip:jh_tutpro_com at 192.168.0.169:5074;transport=udp SIP/2.0
>      Message Header
>          Via: SIP/2.0/UDP 192.98.101.10;branch=z9hG4bKfb.dfd399d1.0
>          From:<sip:click2dial at tutpro.com>;tag=4b2a36a70277f
>          Call-ID: 4b2a36a70277f at tutpro.com
>          To:<sip:jh at tutpro.com>;tag=qpgxk
>          CSeq: 1 ACK
>          User-Agent: SIP Proxy  (2.99.99-pre3 (i386/linux))
>          Content-Length: 0
>
>
>    

-- 
Daniel-Constantin Mierla
* http://www.asipto.com/