officious.
And the easiest way to check for RFC3261-intended-compliance
is the from-tag in the INVITE request - if there isn't a
from-tag, it's an RFC2543 implementation.
Regards,
Attila
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Sourav
and later we are deleting the
transaction because it is wrong ACK.
Your transaction should have been deleted upon sending the 200 OK.
Receipt or none-receipt of ACK is irrelevant.
Thanks Regards,
Shiv
--- On Wed, 18/6/08, Paul Kyzivat [EMAIL PROTECTED] wrote:
From: Paul Kyzivat
is confirmed, but the session SHOULD be
terminated. This is accomplished with a BYE, as described in Section
15.
Regards,
Jitendra.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
JEEVANANDHAM KARTHIC KUMAR
Sent: Wednesday, May 07, 2008 3:05 PM
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
?
For example, in this header:
From: Pepe sip:[EMAIL PROTECTED];phone;online=yes
- header-name = From
- header-value = Pepe sip:[EMAIL PROTECTED];phone;online=yes
- CORE-VALUE = Pepe sip:[EMAIL PROTECTED]
- *(;parameter-name=parameter-value) = ;phone;online=yes
I've found
the same branch id as the
INVITE so they won't have a unique branch-id whereas INVITE and other
requests will always have unique branch ids. I don't see a contradiction
in the text.
Serhad
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
vinodh kumar
-
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: Serhad Doken (serhad) [EMAIL PROTECTED]
Cc: sip-implementors@lists.cs.columbia.edu
Sent: Thursday, November 22, 2007 9:55 AM
Subject: Re: [Sip-implementors] Branch param for CANCEL message
Branch is used to match CANCEL and ACK
Hi,
As per 9.1 Client Behavior of RFC 3261
The following procedures are used to construct a CANCEL request. The
Request-URI, Call-ID, To, the numeric part of CSeq, and From header
fields in the CANCEL request MUST be identical to those in the
request being cancelled, including tags.
Here's a good list. http://www.pernau.at/kd/voip/bookmarks-sip-stacks.html
Of course I have my bias towards OpenSIPStack
MOSBAH ABDELKADER wrote:
Hello all,
I have searched in the internet for an open source and complete C or C++ SIP
stack.
The number was important.
I want to know if
Try OpenSBC. It can be compiled and installed as a windows service.
http://www.opensipstack.org
Tapan Kumar Biswal wrote:
hi
i need an opensource window based SIP server, any please help me to find
it out.
thanks
Tapan
___
For the benefit of the doubter ...
Media sessions can only be changed if the change was offered. 3261
allowed provisional responses which can provide none reliable preview of
the answer. What is not clear was if the preview would be treated as
the final response in case it reached the UAC.
I made a sweeping generalization and included processing of
forked responses.
Paul Kyzivat wrote:
[EMAIL PROTECTED] wrote:
Paul,
I don't think Being strict with what you send and liberal with what
you receive applies in this case. If only the version number
differs, then treat
Scott Lawrence wrote:
On Wed, 2007-07-25 at 11:11 +0800, [EMAIL PROTECTED] wrote:
Hi Everyone,
Recently, I am having problem with one UA that ignores
Proxy-Authorization header if the call-id of the INVITE (Out of Dialog)
is not the same as the one previously challenged. What I am
Scott Lawrence wrote:
On Wed, 2007-07-25 at 23:02 +0800, [EMAIL PROTECTED] wrote:
In all of the above cases, the request is retried by creating a new
request with the appropriate modifications. This new request
constitutes a new transaction and *SHOULD* have the same value
Jeroen van Bemmel wrote:
So the SHOULD covers not only the Call-ID, but also To and From
headers. It is probably a SHOULD because there may be reasons that
from or to headers would be different. The UAC has no valid reason to
use a different Call-ID (and in fact is probably using the same
An error response to an INVITE terminates a transaction. The error MAY
occur before the INVITE reaches the actual destination. Example is a
404 generated by a proxy because it cannot route the INVITE to an actual
UA. A 200 Ok for an INVITE, however, can only be generated by the
BYE with either a different from or to tags
or better yet, use a none existent call-id
sarthakd wrote:
Hi,
I am trying to create an OUT OF DIALOG BYE.
Logically, one of the options would be to change the from or to tags. Just
wanted to know if I send a BYE without 'to' tag, will it be an
17 matches
Mail list logo
