Any idea why 192.168.0.159  send CANCEL on packet #4?

o.     Time                       Source                Sport  Destination      
     Dport  RawProto   Protocol Length VlanId Dscp Info
      1 2014-06-04 16:24:03.038997 192.168.0.159       64038  192.168.0.112     
  5060   TCP        SIP/SDP  1020          0    Request: INVITE 
sip:[email protected];transport=tcp | 
      2 2014-06-04 16:24:03.039049 192.168.0.112       5060   192.168.0.159     
  64038  TCP        TCP      56            0    sip > 64038 [ACK] Seq=1 Ack=965 
Win=114 Len=0
      3 2014-06-04 16:24:03.041056 192.168.0.112       5060   192.168.0.159     
  64038  TCP        SIP      510           0    Status: 100 Trying | 
      4 2014-06-04 16:24:03.049601 192.168.0.159       64038  192.168.0.112     
  5060   TCP        SIP      509           0    Request: CANCEL 
sip:[email protected];transport=tcp | 
      5 2014-06-04 16:24:03.050163 192.168.0.112       5060   192.168.0.158     
  49896  TCP        TCP      1316          0    [TCP segment of a reassembled 
PDU]
      6 2014-06-04 16:24:03.050195 192.168.0.112       5060   192.168.0.158     
  49896  TCP        SIP/SDP  560           0    Request: INVITE 
sip:[email protected]:49896;transport=tcp;rinstance=427b47a968808703 | 
      7 2014-06-04 16:24:03.050493 192.168.0.112       5060   192.168.0.159     
  64038  TCP        SIP      425           0    Status: 200 OK | 
      8 2014-06-04 16:24:03.051171 192.168.0.158       49896  192.168.0.112     
  5060   TCP        TCP      62            0    49896 > sip [ACK] Seq=1 
Ack=1765 Win=16695 Len=0
      9 2014-06-04 16:24:03.051729 192.168.0.112       5060   192.168.0.158     
  49896  TCP        SIP      440           0    Request: CANCEL 
sip:[email protected]:49896;transport=tcp;rinstance=427b47a968808703 | 
     10 2014-06-04 16:24:03.064229 192.168.0.158       49896  192.168.0.112     
  5060   TCP        SIP      471           0    Status: 200 OK | 
     11 2014-06-04 16:24:03.064266 192.168.0.112       5060   192.168.0.158     
  49896  TCP        TCP      56            0    sip > 49896 [ACK] Seq=2149 
Ack=416 Win=89 Len=0
     12 2014-06-04 16:24:03.066223 192.168.0.158       49896  192.168.0.112     
  5060   TCP        SIP      803           0    Status: 487 Request Terminated 
| 
     13 2014-06-04 16:24:03.066248 192.168.0.112       5060   192.168.0.158     
  49896  TCP        TCP      56            0    sip > 49896 [ACK] Seq=2149 
Ack=1163 Win=88 Len=0
     14 2014-06-04 16:24:03.066608 192.168.0.112       5060   192.168.0.158     
  49896  TCP        SIP      447           0    Request: ACK 
sip:[email protected]:49896;transport=tcp;rinstance=427b47a968808703 | 
     15 2014-06-04 16:24:03.259855 192.168.0.159       64038  192.168.0.112     
  5060   TCP        TCP      62            0    64038 > sip [ACK] Seq=1418 
Ack=824 Win=16120 Len=0
     16 2014-06-04 16:24:03.259894 192.168.0.112       5060   192.168.0.159     
  64038  TCP        SIP      453           0    Status: 487 Request Terminated 
| 
     17 2014-06-04 16:24:03.262852 192.168.0.159       64038  192.168.0.112     
  5060   TCP        SIP      469           0    Request: ACK 
sip:[email protected];transport=tcp | 
     18 2014-06-04 16:24:03.270988 192.168.0.158       49896  192.168.0.112     
  5060   TCP        TCP      62            0    49896 > sip [ACK] Seq=1163 
Ack=2540 Win=16501 Len=0
     19 2014-06-04 16:24:03.300786 192.168.0.112       5060   192.168.0.159     
  64038  TCP        TCP      56            0    sip > 64038 [ACK] Seq=1221 
Ack=1831 Win=115 Len=0


-----Original Message-----
From: PS 
Sent: Wednesday, June 04, 2014 6:00 PM
To: [email protected]
Subject: Question on creating SIP call 

Hi

I faced a problem on creating a SIP call between two X-Lite client.

I observed that Client A send SIP REQUEST CANCEL after 100 Trying. Is there any 
reason on this?

- PS
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater

Reply via email to