[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    Re: [Sip-implementors] Proxy Timer C processing - how does it help?
From:       "Song, Youngsun" <ysong () telcordia ! com>
Date:       2006-05-31 23:55:28
Message-ID: 5D21DF1BB43D0C4F8473E6202EF99757058FC843 () rrc-dte-exs02 ! dte ! telcordia ! com
[Download RAW message or body]

Sachin,



YoungSun 

> -----Original Message-----
> From: sip-implementors-bounces@cs.columbia.edu 
> [mailto:sip-implementors-bounces@cs.columbia.edu] On Behalf Of Sachin
> Sent: Thursday, May 04, 2006 5:58 AM
> To: sip-implementors@cs.columbia.edu
> Subject: [Sip-implementors] Proxy Timer C processing - how 
> does it help?
> 
> Hello,
> 
> According to RFC if Timer C fires at proxy, it should 
> generate CANCEL (provided 1xx was received). Now if the 
> CANCEL gets 200 OK but the original INVITE does not receive 
> any final response, what should the proxy do? Won't the 
> INVITE client transaction continue to hang forever? Won't 
> this beat the purpose of Timer C, which is there...
> 
> "In order to handle the case where an INVITE request *never* 
> generates a final response,..."
> 
> 
>          INV              INV
> UAC ------------> P1 --------------> UAS
>          100              100
>     <------------    <--------------
> 
>            [Timer C Fires]
>                           CANCEL
>                      --------------->
>                           200(CANCEL)
>                      <---------------
> 
>      [No final for INVITE yet.]
> 
> 
> Thanks,
> Sachin
>                     
> 16.8 Processing Timer C
> 
> "   If timer C should fire, the proxy MUST either reset the timer with
>    any value it chooses, or terminate the client transaction.  If the
>    client transaction has received a provisional response, the proxy
>    MUST generate a CANCEL request matching that transaction.  If the
>    client transaction has not received a provisional 
> response, the proxy
>    MUST behave as if the transaction received a 408 (Request Timeout)
>    response."
> 
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
> 


[prev in list] [next in list] [prev in thread] [next in thread]