Re: [Sip-implementors] re-transmission timer for UAC transaction (INVITE) failed

able to respond to 2xx of corresponding INVITE. -- If timer B fails then terminate the INVITE transaction and responses for that INVITE needs to be dropped. Thanks and regards, Praveen Dandin - Date: Tue, 14 Oct 2008 15:16:58 +0200 From: "

[Sip-implementors] CANCEL request without branch parameter

17.2.3 description) are identical?? Thanks, Praveen Dandin - Bring your gang together. Do your thing. Find your favourite Yahoo! Group. ___ Sip-implementors mailing list Sip-implementors

[Sip-implementors] Is port be included in Request-Uri if the hostport is hostname??

hostname is present in Request-URI or Contact (like INVITE sip:[EMAIL PROTECTED] SIP/2.0) is it valid to include the port number in the URI (like INVITE sip:[EMAIL PROTECTED]:8080 SIP/2.0). I feel the mentioned SIP address' port can be resolved at UAS end throug

Re: [Sip-implementors] Can PRACK be challenged??

after receiving the PRACK.If it so, then the PRACK with credentials will not have the matching RPR as the RPR will get removed when first PRACK is received. Is this not contradicting with the above statement(i.e., statement from 3262 section 3)?? Thanks, Praveen Dandin Paul Kyzivat <[EM

Re: [Sip-implementors] Can PRACK be challenged??

ues in RAck of PRACK but not its Cseq with that of RPR?? I did not find any relevant data to handle such a scenario from RFCs 3261 n 3262. Is there any draft which addresses such a scenario? Thanks, Praveen Dandin Paul Kyzivat <[EMAIL PROTECTED]> wrote: I can'

[Sip-implementors] Can PRACK be challenged??

credentials after receiving a 401 (Unauthorized) or 407 (Proxy Authentication Required) response, it MUST increment the CSeq header field value as it would normally when sending an updated request."] 4) How the PRACK transactions be maintained in this case? Please provide your valuable

[Sip-implementors] CANCEL and 2xx(INVITE) race condition

ely no-op}. Please provide your valuable inputs. Thanks, Praveen Dandin - Share files, take polls, and make new friends - all under one roof. Click here. ___ Sip-implementors mailing list Sip-implemen

Re: [Sip-implementors] Should 200 OK be sent to UPDATE received withSession-Expires in early dialog?

reINVITE) with SE header while the UAS is processing reINVITE refresh request, then should UAS send the 4xx-5xx response to such an UPDATE? [ As per the discussion so far the answer to this question is NO. If it is otherwise please let me know]. Thanks, Praveen Dandin Brett Tate

Re: [Sip-implementors] Should 200 OK be sent to UPDATE received withSession-Expires in early dialog?

Hi all, One more query is added to the list of queries as compared to previous mail:) praveen dandin <[EMAIL PROTECTED]> wrote:Hi Paul/Harsha/Brett, What I understood from the discussion is : If one session timer negotiation is under process (received through INVITE ), processi

Re: [Sip-implementors] Should 200 OK be sent to UPDATE received withSession-Expires in early dialog?

n-timer by including the Session-Expires header]. 5) Is there any RFC statement which says that "An outstanding session-expires mechanism should not prevent another from occurring." ?. If so, please let me know. Thanks, Praveen Dandin Paul Kyzivat <[EMAIL PROTECTE

[Sip-implementors] Should 200 OK be sent to UPDATE received with Session-Expires in early dialog?

ehaviour? Or should it be rejected with any failure response 4xx-6xx? Please provide your valuable suggestions. Thanks and regards, Praveen Dandin - Why delete messages? Unlimited storage is just a click away. __

Re: [Sip-implementors] Query on UAC behaviour when supporting sessiontimer

Hi, The section 11.1 of RFC 4028 talks about the possible behavior of the proxy in this case when it states the following: "The proxies will reject this request and provide a Min-SE with a higher minimum, which the UAC will then use. Note, that if the proxies did not reject the request, bu

[Sip-implementors] Query on UAC behaviour when supporting session timer

200 OK and sets the value of session-interval to the value 'y' (i.e, it increases the value of session-expires 'z' to value of MinSE 'y' the least value which the UAC was expecting) and starts the session timer. Please let

Re: [Sip-implementors] ACKing 200 OKs

s each 2xx response to INVITE and its corresponding ACK.” Regards, Praveen Dandin - Bring your gang together - do your thing. Start your group. ___ Sip-implementors mailing list Sip-im

Re: [Sip-implementors] Is session-expires be sent in 2xx response eventhough UAS doesnt support session timer?

there exist some exceptions? Thanks, Praveen Dandin Attila Sipos <[EMAIL PROTECTED]> wrote: >>This is as per section 9 statement of draft: draft-ietf-sip-session-timer-10.txt >> If the UAS wishes to accept the request, it copies the value of >>the Session-Expir

[Sip-implementors] Is session-expires be sent in 2xx response even though UAS doesnt support session timer?

f UAS. Also the draft says that the session timer extension has the property that it works even when only one UA in a dialog supports it. So what should be the behaviour of UAC (which is supporting session timers) in case UAS does not support session timers?. Thanks, Praveen D

Re: [Sip-implementors] Is route set be recomputed while sending ACKfor retransmitted 2xx?

-Original Message- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On >> Behalf Of praveen dandin >> Sent: Friday, October 19, 2007 12:13 AM >> To: Nebojsa Miljanovic >> Cc: Sip-implementors@lists.cs.columbia.edu >> Subject: Re: [Sip-implemento

Re: [Sip-implementors] Is route set be recomputed while sending ACK for retransmitted 2xx?

rds, Praveen Nebojsa Miljanovic <[EMAIL PROTECTED]> wrote: Since 200 OK responses must follow the Vias listed in INVITE, they cannot be retransmitted over different proxies. On 10/17/2007 2:12 AM, praveen dandin wrote: > Hi, > Consider the followin

[Sip-implementors] Is route set be recomputed while sending ACK for retransmitted 2xx?

Hi, Consider the following scenario ( proxies between UAC and UAS are not shown) UAC UAS INVITE |>| 180 |<--