On the other hand we also have the following -which seems contradicting to
the statement in 28.1, that simultaneous transactions from the same UA are
allowed in a dialogue-
12.2.2 UAS Behavior
"If the remote sequence number was not empty, and the sequence number of the
request is lower than the remote sequence number, the request is out of
order and MUST be rejected with a 500(Server Internal Error) response."
If the second request is sent before waiting the first one to complete, I
think for UDP we might have a race condition, where second request arrives
before the first one, which would force the first request -which arrives
later- to be rejected.
Tolga
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Pinal
> Jean-Pierre
> Sent: Tuesday, December 16, 2003 11:14 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [Sip-implementors] 2 requests at the same time?
>
>
>
> Hi
>
> I think that RFC 3261 provides the answer in different places:
>
> 1)
> SIP Transaction: A SIP transaction occurs between a client and a
> server and comprises all messages from the first request sent
> from the client to the server up to a final (non-1xx) response
>
> 2)
> 13.2.2 Processing INVITE Responses
>
> Once the INVITE has been passed to the INVITE client transaction, the
> UAC waits for responses for the INVITE.
> However, a UA MAY initiate a regular transaction while an INVITE
> transaction is in progress. A UA MAY also initiate an INVITE
> transaction while a regular transaction is in progress.
>
>
> 20.16 CSeq
>
> A CSeq header field in a request contains a single decimal sequence
> number and the request method. The sequence number MUST be
> expressible as a 32-bit unsigned integer. The method part of CSeq is
> case-sensitive. The CSeq header field serves to order transactions
> within a dialog, to provide a means to uniquely identify
> transactions, and to differentiate between new requests and request
> retransmissions.
>
> And in conclusion in RFC:
>
> 28.1 Major Functional Changes
>
> RFC 2543 was silent on whether a UA could initiate a new
> transaction to a peer while another was in progress. That is now
> specified here. It is allowed for non-INVITE requests, disallowed
> for INVITE.
>
> If I well understand, it is allowed for no INVITE transaction and
> it is the role of UA transaction user to reorder the transaction
> thanks Cseq.
>
> It would be nice if other people can confirm that.
>
> Best regards
>
> Jean-Pierre
>
>
> -----Original Message-----
> From: Ar c'hasour [mailto:[EMAIL PROTECTED]
> Sent: mardi 16 d�cembre 2003 14:48
> To: [EMAIL PROTECTED]
> Subject: [Sip-implementors] 2 requests at the same time?
>
> Hi,
>
> I have a basic question about SIP, which I can not
> find the answer in 3261, nor 3265.
>
> Once a dialog is established, can a UA send 2 SIP
> requests at the same time (eg: 2 NOTIFY) in this
> dialog, or must he send the 1st SIP request, wait for
> the response for the 1st request, and only then send
> the 2nd SIP request?
>
> Thanks
> Patrig
>
> __________________________________
> Do you Yahoo!?
> New Yahoo! Photos - easier uploading and sharing.
> http://photos.yahoo.com/
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
