>> 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
I think the header is well formed (grammatically correct), but it has no
semantics in ACK message.
On Thu, Apr 3, 2008 at 11:34 AM, Pandurangan R
>> 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
I think the header is well formed (grammatically correct), but it has no
sementics in ACK message.
On Wed, Apr 2, 2008 at 9:32 PM, Singh, Indresh
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 | diversi
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 use
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 with
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 s
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 = "reas
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 t
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 (t
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
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 someth
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, a
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
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
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
If offer is in 183 and Prack is enabled, then yes answer sdp must be in
Prack.
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, April 02, 2008 7:59 AM
>To: Sanjay Sinha (sanjsinh)
>Cc: Nithin N; sip-implementors@lists.cs.columbia.edu
>Subject: Re:
[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
>
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.
Joegen
Paul Kyzivat wrote:
> Yes, of course it can be sent in the PRACK. Its one of the primary
> purposes of PRACK.
>
>
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 termina
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 Serv
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 N
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
>Sent: Wednesday, April 02, 2008 7:24 AM
>To: sip-implementors@lists.cs.columbia.edu
>Subject: [Sip-implementors] Offer/Answer Violat
Hi All
If an Offer/Answer violation happens in RPR case, how shall we terminate the
dialog. For example, if PRACK is received with a malformed SDP, what
shall be the error response code that needs to be sent to UA.
UA SBCProxy
| INVITE
23 matches
Mail list logo
