Re: [Sip-implementors] Offer/Answer Violation in RPR Cases

2008-04-02 Thread [EMAIL PROTECTED]
Can the SDP answer be actually sent through PRACK? Shouldn't it be sent in ACK for 200 Ok? Sanjay Sinha (sanjsinh) wrote: 200 OK to the Prack and then terminate the Invite with 488. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nithin N

Re: [Sip-implementors] Conflict of Information sent in two tuples

2008-04-02 Thread santoshkumar pati
Can Anybody give some test cases both Positive and negative Test Cases For Call Hold feature.. Regards Santosh pati System Test Engineer Infovista Technology inc.. On 3/3/08, chom sri [EMAIL PROTECTED] wrote: Hi , What are the real life scenario use cases where the Presence Server

Re: [Sip-implementors] Offer/Answer Violation in RPR Cases

2008-04-02 Thread Paul Kyzivat
Yes, of course it can be sent in the PRACK. Its one of the primary purposes of PRACK. Paul [EMAIL PROTECTED] wrote: Can the SDP answer be actually sent through PRACK? Shouldn't it be sent in ACK for 200 Ok? Sanjay Sinha (sanjsinh) wrote: 200 OK to the Prack and then terminate

Re: [Sip-implementors] Offer/Answer Violation in RPR Cases

2008-04-02 Thread Paul Kyzivat
[EMAIL PROTECTED] wrote: Paul, I must admit I am surprised by this. I thought offers and answers can only be sent using the same transaction. Thanks for clearing it out. I have some code to fix. See http://www.ietf.org/internet-drafts/draft-ietf-sipping-sip-offeranswer-06.txt

[Sip-implementors] Require: 100rel in ACK

2008-04-02 Thread kavitha.subramaniam
Hi All, I have got a question about Require: 100rel in ACK Request. Presence of Require: 100rel header in ACK request is allowed? RFC 3262 says A Require header with the value 100rel MUST NOT be present in any requests excepting INVITE, although extensions to SIP may allow its usage with other

[Sip-implementors] Require: 100rel in ACK

2008-04-02 Thread kavitha.subramaniam
Hi All, I have got a question about Require: 100rel in ACK Request. Presence of Require: 100rel header in ACK request is allowed? RFC 3262 says A Require header with the value 100rel MUST NOT be present in any requests excepting INVITE, although extensions to SIP may allow its usage with other

Re: [Sip-implementors] FW: Require: 100rel in ACK

2008-04-02 Thread Robert Sparks
Without looking at the specs, here's what I believe they say (I'll chase down text later if you really need me to). In any case, this is what you should do for maximum interoperability: Don't put Require: 100rel in an ACK. Don't get upset if someone else does - ignore it. RjS On Apr 2, 2008,

Re: [Sip-implementors] FW: Require: 100rel in ACK

2008-04-02 Thread Robert Sparks
btw - the line in 3261 that you quote below is intended to mean that the ACK Require tokens must be a subset of the INVITE Require tokens. It is not intended to say that the ACK Require tokens be exactly the set of INVITE Require tokens. Specifically, its point is that you can't Require

Re: [Sip-implementors] Require: 100rel in ACK

2008-04-02 Thread Singh, Indresh (NSN - US/Boca Raton)
Refer to table 2 page 163 of RFC3261. You will find that require header itself is not allowed in ACK requests. Regards, Indresh -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ext kavitha.subramaniam Sent: Wednesday, April 02, 2008 1:10 AM To:

Re: [Sip-implementors] FW: Require: 100rel in ACK

2008-04-02 Thread Singh, Indresh (NSN - US/Boca Raton)
I agree with Robert w.r.t to best results for inter-operability, I think this should be treated as malformed header field for ACK request ( It is not expected to be included in ACK ) and thus should be ingored 8.2.2 Header Inspection If a UAS does not understand a header field in a request

Re: [Sip-implementors] Steps of Transport Layer when receiving a request

2008-04-02 Thread Iñaki Baz Castillo
El Monday 31 March 2008 22:09:19 Iñaki Baz Castillo escribió: Hi, I'm trying to get the steps the Transport Layer must perform when receiving a request, but it doesn't seem to appear very clear in RFC 3261 (at last I cannot find them). I've compiled the steps I've found and would like to know

Re: [Sip-implementors] rfc3261 and rfc4485: gen-value and quoted-string

2008-04-02 Thread Robert Sparks
In general, any literal 's that appear in a BNF rule are not quotes you will see in messages formed from that grammar. There will be a rule (in 3261's case it is DQUOTE) that represents those. That's not going to help with display-name, since the DQUOTEs are part of that expansion, but it

[Sip-implementors] rfc3261 and rfc4485: gen-value and quoted-string

2008-04-02 Thread Brett Tate
Greetings, Concerning rfc3261 and rfc4485 usage of gen-value and quoted-string, are the quotes considered part of the value during use? Since I didn't notice a good example within rfc3261, I'll ask more specifically concerning the forbidden draft-levy-sip-diversion. :) diversion-reason =

Re: [Sip-implementors] rfc3261 and rfc4485: gen-value and quoted-string

2008-04-02 Thread Paul Kyzivat
I agree with Robert. The following is a more direct answer to your specific question. Brett Tate wrote: Greetings, Concerning rfc3261 and rfc4485 usage of gen-value and quoted-string, are the quotes considered part of the value during use? Since I didn't notice a good example within

[Sip-implementors] Using SUBSCRIBE/NOTIFY

2008-04-02 Thread Senthil-Raja C.
Hello All, I am trying to develop a SIP implementation framework to enable a UAC to receive confirmation if the MESSAGE is actually read by the User. RFC 3428 doesn't supports this. Is it possible that UAC uses the Event header of SUBSCRIBE method for requesting the UAS to send NOTIFY when the

Re: [Sip-implementors] rfc3261 and rfc4485: gen-value andquoted-string

2008-04-02 Thread Avasarala Ranjit-A20990
Hi Paul Below is the semantics for the diversion header from the draft The syntax of the Diversion header is: Diversion = Diversion : 1# (name-addr *( ; diversion_params )) diversion-params = diversion-reason | diversion-counter | diversion-limit |