Iñaki Baz Castillo wrote:
> Hi,
>
> It's very common that when a UA1 sends a REGISTER via TCP from a random port
> 1, if the connection remains open (for example using ping-pong method),
> the proxy can send request to UA1 using that TCP connection.
> Is really this behaviour defined in RF
Anuradha Gupta wrote:
> How to maintain multiple dialogs should be implementation specific.
> RFC 3261 explains about forking at multiple places.
> As the forked reponses differ on "To Tag" therefore multiple dialogs need to
> be maintained on the basis of To Tags till the time forked provisiona
2008/10/13 Attila Sipos <[EMAIL PROTECTED]>:
>>>but I really wonder
>>>which is the difference between this case and the above case in which UA1
>>>receives incoming requests from the proxy using the port 1 used for
>>>registration.
>
> I agree, I don't think there is much difference.
> Except
In case there are multiple load balancer, Record-Route need to be filled with
custom name, value tag. This is done so that once dialog is made, all further
messages follow same selected server (which was first selected by load
balancer).
-
Vipul
-Original Message-
From: [EMAIL PROTECTED
>>It's very common that when a UA1 sends a REGISTER via TCP from a random port
>>1,
>>if the connection remains open (for example using ping-pong method), the
>>proxy can
>>send request to UA1 using that TCP connection.
>>Is really this behaviour defined in RFC 3261?
I can't see that it is d
I feel a 400 Bad Request response with Reason phrase as "Missing
Content-type header field" is appropriate for this scenario
E.g. 400 Bad request SIP/2.0
..
..
Reason: Missing content-type header field
Regards
Ranjit
-Original M
Hi,
"400 Missing Content-Type header field" error response is appropriate as
mandatory header is missing in this PDU:
As per RFC-3261
20.15 Content-Type
The Content-Type header field indicates the media type of the
message-body sent to the recipient. The "media-type" element is
defined
No, then the user would look for the codec mismatch in the SDP.
We need to use a response which helps the user find the problem.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Anuradha Gupta
Sent: 13 October 2008 08:22
To: Rohit Aggarwal; sip-implemen
Hi
How would the UAS know whether the received media description is acceptable or
not, unless it parses it using the Content-Type header value? In that case, 415
and 488 may not be appropriate responses.
Regards
Rohit Aggarwal
Aricent
-Original Message-
From: [EMAIL PROTECTED] [mailto:
400 "Bad request" can also be send when some mandatory header is missing. :)
Cheers,
Vivek
Rancore Technologies
More computing sins are committed in the name of efficiency (without
necessarily achieving it) than for any other single reason - including blind
stupidity."
"On the other hand, we ca
Hi,
I think 415 Unsupported Media Type is a better response.
Thanks,
K.Prateep
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Rohit Aggarwal
Sent: Monday, October 13, 2008 12:48 PM
To: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implemen
400 bad request should be sent for syntactical errors, in the received PDU
there is no syntactical error.
Can "488 not acceptable here" be sent with warning header?
Regards
Anuradha Gupta
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rohit Aggarwal
Se
I'd go for "400 Bad Request"
You can specify other text if you like "400 Bad Request No Content Type"
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Anuradha Gupta
Sent: 13 October 2008 08:15
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-im
How about 400 Bad Request with an appropriate reason-phrase like "Missing
Content-Type header field"?
Regards
Rohit Aggarwal
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anuradha Gupta
Sent: Monday, October 13, 2008 12:45 PM
To: sip-implementors@lists
Hi
If reINVITE is received with SDP body but the content -type header is missing
then it should be rejected with what response code.
The sample reINVITE is:
INVITE sip:[EMAIL PROTECTED]:3819 SIP/2.0
To: 3275;tag=AricentUA_816059597-27872
From: 444;tag=abc
Call-ID: 5486
CSeq: 3 INVITE
Via: SIP/2
15 matches
Mail list logo
