Paul
My understanding is the same as yours.
Venkat
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of
Paul Kyzivat (pkyzivat)
Sent: Wednesday, February 17, 2010 3:48 PM
To: SIP-implementors mailing l
> From: Mark R Lindsey [mailto:lind...@e-c-group.com]
>
> You're going to have to clarify this use case a little more -- as you
> said, it doesn't follow the SIP transaction model, so it's hard to
> quite see what you mean. Can you give more detail?
>
Sure. In this case my SIP client is contained
On Feb 17, 2010, at 9:50 PM, Aaron Clauson wrote:
>
> I have a scenario where I want a SIP client to be able to generate
> multiple
> redirect responses. The redirect responses will be generated based
> on user
> actions and will have a variable delay between them.
You're going to have to cla
Hi,
I have a scenario where I want a SIP client to be able to generate multiple
redirect responses. The redirect responses will be generated based on user
actions and will have a variable delay between them.
As far as I can see there is no standard's compliant way to achieve that
since the first
I got queried about this when an interop problem popped up.
I know what I think the right answer is, but want to check what others
think.
Here is the case:
Alice calls Bob:
INVITE ...
From: ;tag=;foo=bar
this succeeds and a dialog is established.
Then, within that dialog, Bob sends a
sunilkumar.ve...@wipro.com wrote:
> Hi,
>
> We can user multiple m line in the offer to take care of both V4 and
> V6.
> Also you can refer ANAT RFC for SDP negotiation.
Note that when ice becomes and RFC, it will deprecate ANAT
(see http://tools.ietf.org/html/draft-ietf-mmusic-ice-19).
ICE is
Hi,
We can user multiple m line in the offer to take care of both V4 and
V6.
Also you can refer ANAT RFC for SDP negotiation.
Regards
Sunil Verma
ESN: 877-5050
Ph: +919731245000
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun..
Klaus Darilion wrote:
> Hi!
>
> Consider the simple scenario: caller is dual-stacked and supports IPv4
> and IPv6. When creating the SDP, the caller does not know if callee use
> IPv4-only, IPv6-only or is dual-stacked too.
>
> SIP probably is not an issue and will be done by the proxies - but
Look at http://tools.ietf.org/html/draft-ietf-sipping-v6-transition-07
> -Original Message-
> From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-
> implementors-boun...@lists.cs.columbia.edu] On Behalf Of Klaus Darilion
> Sent: Wednesday, February 17, 2010 8:44 AM
> To: sip-
Hi!
Consider the simple scenario: caller is dual-stacked and supports IPv4
and IPv6. When creating the SDP, the caller does not know if callee use
IPv4-only, IPv6-only or is dual-stacked too.
SIP probably is not an issue and will be done by the proxies - but what
about finding the proper IP ve
10 matches
Mail list logo
