Hi, I was discussing the timer value of 64*T1 only.Here from my UAC side we had set a timer of T1=500.Therefore the 64*T1 comes out to be 32sec.The initial INVITE message being sent at 15:51:00 and the timer expires at 15:51:32 .Since final response is coming at 15:52:00 ,my MSC i.e UAC here is cancelling the end to end and probably sending the disconnect message to UE.
I think we need to analyze the timer expiry at PROXY side.Isnt it? ________________________________ From: Brett Tate <br...@broadsoft.com> To: sampat patnaik <sam_e...@yahoo.co.in>; "sip-implementors@lists.cs.columbia.edu" <sip-implementors@lists.cs.columbia.edu> Sent: Tuesday, 24 September 2013 12:56 AM Subject: RE: [Sip-implementors] SIP ISSUE > In my case The original Invite Message has been sent > at 15:51:00 and CANCEL request sent at 15:51:16 from > UAC i.e(SOURCE) and is being acknoledged with 200 OK > at 15:51:16 by the PROXY. However the same PROXY is > sending the error SERVER TIMEOUT at 15:52:00 which > is more than the time(64*T1) specified/allowed to > respond to original INVITE request . The mentioned 64*T1 time does not apply to the proxy/UAS. That is the suggested time for the UAC which sent CANCEL to wait for INVITE transaction completion. > So my question on TIMER expiry seems to be a valid one > as to why the SBG (PROXY) is not responding on time > (pls note that the time difference between 7th INVITE > and 504 Message is again 30secs. Does the SBG takes > that much time to respond? You'd need to ask the vendor. However based upon what you provided, it sounds like T1 might be configured to be around 1 second or Timer B is configured to be 60 seconds. > What should be the time to respond to source indicating > the reason of time out? >From a UAC perspective, you are aware of the recommended wait time. From a >proxy perspective, it may or may not return the final response within the >interval expected by the UAC. However as far as I know, RFC 3261 allows the >proxy to basically act as it wants concerning the topic since it doesn't >mandate that T1 be 500ms. Thus, the reason why you are experiencing all of >the retries. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
