Paul already answered your question, but as a side note - I strongly encourage
you to NEVER put a 100rel in a Require header. What you're basically saying by
doing that is: "this call CANNOT and MUST NOT succeed if the far-end UAS it
reaches doesn't support reliable provisional responses". Ve
Michael Hirschbichler wrote:
> Thx, I got it :)
>
> 2nd question in this context: If in an INVITE-request an "Allow: PRACK,
> ..."-Header is set, am I correct in the assumption, that there must be a
> "supported: 100rel"-Header too?
Logically they are distinct. So "in principle" you could sup
Thx, I got it :)
2nd question in this context: If in an INVITE-request an "Allow: PRACK,
..."-Header is set, am I correct in the assumption, that there must be a
"supported: 100rel"-Header too?
br
Michael
Am 06.05.2010 15:45, schrieb Paul Kyzivat:
>
>
> Michael Hirschbichler wrote:
>> Hi all,
Hi,
Can we have an implementation like the one shown below. I want to establish
a Video/Audio session between Sip endpoint (S1) and Sip endpoint (S2). I am
using Freeswitch (FS) for signaling. The steps are mentioned below
* FS will initiate a call to S1. S1 will send its Audio RTP and Vid
Michael Hirschbichler wrote:
> Hi all,
>
> we are currently discussing if it is possible (and - esp. - allowed) to
> set both, a "Require:"- and a "Supported:"-Header with the
> "100rel"-option in the same INVITE-Request. In my opinion, if 100rel is
> set in the "Require:"-header, it is impli
Hi all,
we are currently discussing if it is possible (and - esp. - allowed) to
set both, a "Require:"- and a "Supported:"-Header with the
"100rel"-option in the same INVITE-Request. In my opinion, if 100rel is
set in the "Require:"-header, it is implicitely also supported and
should not expli
> Sharanabasavaraj Mathapati
> Sent: Thursday, 6 May 2010 5:23 PM
> To: sip-implementors@lists.cs.columbia.edu
> Subject: [Sip-implementors] Query on REGISTER message
>
> What if DE-REGISTER message receives 401? Should we send again a
> DE-REGISTER message with authentication details?
You wouldn
What would you do if the SIP response's signature was invalid? A SIP response
can't be rejected. For example, you can't tell the responder that it needs to
send the response again with a new signature if the signature it sent had an
error or was stale. And the verifier of the identity signat
> -Original Message-
> From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-
> implementors-boun...@lists.cs.columbia.edu] On Behalf Of Sharanabasavaraj
> Mathapati
>
> Should we wait for response when we send DE-REGISTER message?
Yes.
> What if DE-REGISTER message receiv
The authoritative source for that is:
http://www.iana.org/assignments/sip-parameters
Scroll down a page or so, and look for the table column labeled "compact". (the
"short form" is called the "compact form" in RFC3261)
-hadriel
> -Original Message-
> From: sip-implementors-boun...@lists
Hi All,
Should we wait for response when we send DE-REGISTER message?
What if DE-REGISTER message receives 401? Should we send again a
DE-REGISTER message with authentication details?
Regards,
Sharan
11 matches
Mail list logo
