[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    Re: [Sip-implementors] Section 4 in RFC 3891 - UAC behavior
From:       Back To Back User Agent <sipb2bua () gmail ! com>
Date:       2009-06-17 11:16:13
Message-ID: 8c8d3cb50906170416k77b5f2bbw8d8d7f0f436e3233 () mail ! gmail ! com
[Download RAW message or body]

Hello,

Thank you for your answers. I missed the part where it says that
INVITE w/ Replaces matches a single dialog and therefore will not get
forked at a state full proxy.

The other mail-thread "Early dialog can be replaced if Transfer Target
is the recipient of dialog (early) during Attendant Call Transfer" -
mostly discusses the forking case as well.

Is the only option left for Alice simply to try a new call after its
IP address changes? Would this behavior be acceptable to you?

Thanks,
Vishal

On Wed, Jun 17, 2009 at 1:19 AM, Iñaki Baz Castillo<ibc@aliax.net> wrote:
> El Miércoles, 17 de Junio de 2009, Back To Back User Agent escribió:
>> Hi,
>>
>> Section 4 in RFC 3891 says the following:
>>
>> A UAC MUST NOT send an INVITE with a Replaces header field that
>> attempts to replace an early dialog which was not originated by the
>> target of the INVITE with a Replaces header field.
>>
>> Could you please shed some light why this restriction was put in
>> place? Is my understanding of the above text in RFC wrong for my use
>> cases?
>>
>> I have couple of use cases where it would be better if this
>> restriction wasn't there...
>
>
> Basically the problem could occur when there is forking.
>
> Also, this subject has already taken place in this maillist. Please check in
> this page the mails with subject:"
>
>   "Early dialog can be replaced if Transfer Target is the reciepient of
>    dialog (early) during Attendant Call Transfer".
>
>    https://lists.cs.columbia.edu/pipermail/sip-implementors/2009-
> May/date.html#22641
>
>
>
> --
> Iñaki Baz Castillo <ibc@aliax.net>
>
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>


[prev in list] [next in list] [prev in thread] [next in thread]