On Wed, 2009-05-06 at 17:55 -0700, Vikram Chhibber wrote:
> I can not think of any reason why RFC did not allow replacement of
> early dialog at the UAS.
The reason that the replacement of an incoming early dialog is not
allowed is the complexity that would be introduced if the caller has
multiple
On Wed, 2009-05-06 at 10:11 +0530, Vivek Batra wrote:
> If we correlate the above RFC statement with the Attendant Call Transfer,
> does it mean that if Transfer Target receives the INVITE (replaces) header
> and it matches with the early dialog which is not initiated by the transfer
> target, tran
On Thu, 2009-05-07 at 21:44 +0200, Iñaki Baz Castillo wrote:
> El Jueves, 7 de Mayo de 2009, Vikram Chhibber escribió:
>
> > I could not think of
> > any useful case for early dialog getting replaced at UAS end.
>
> Let me tell an example (real example):
>
> - A calls B.
> - B answers.
> - B wan
On Thu, 2009-05-07 at 12:08 +0530, Rastogi, Vipul (Vipul) wrote:
> I don't know if sending 487 after 180 is good idea. I have seen
> following in few places ...
If the caller cancels the call while it is ringing, the UAS has no
choice but to send a 487 after it sends a 180.
Dale
___
El Jueves, 7 de Mayo de 2009, Vikram Chhibber escribió:
> I could not think of
> any useful case for early dialog getting replaced at UAS end.
Let me tell an example (real example):
- A calls B.
- B answers.
- B wants to transfer the call to C.
- So B puts A on-hold and calls C.
- C doesnt' answ
rom: Vikram Chhibber [mailto:vikram.chhib...@gmail.com]
> Sent: Thursday, May 07, 2009 3:25 AM
> To: Vivek Batra
> Cc: sip-implementors@lists.cs.columbia.edu
> Subject: Re: [Sip-implementors] Early dialog can be replaced if Transfer
> Target is the reciepient of dialog (early) during Att
arly dialog can be replaced if Transfer Target
is the reciepient of dialog (early) during Attendant Call Transfer
Vikram/Vipul,
Regarding definition of Attendant Transfer, most of the Analog/ Digital PBX
allows you to perform the Attendant Transfer activity even when Transfer Target
is in ringin
, 2009 3:25 AM
To: Vivek Batra
Cc: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] Early dialog can be replaced if Transfer
Target is the reciepient of dialog (early) during Attendant Call Transfer
On Tue, May 5, 2009 at 9:41 PM, Vivek Batra
wrote:
> Hi Folks,
>
> I
I can not think of any reason why RFC did not allow replacement of
early dialog at the UAS. I can think of one more feature for this
case. For example, the caller wanted to initiate an audio session,
the called party did not respond in time and then the caller decided
to leave an instant message u
An example of service using "replacing the early dialog _initiated_ by
UA" could be a call-collect feature where the receiver does not want
the originator to be charged for the call, the receiver calls back the
originator. I could not think of service using "replacing the early
dialog _not_ initiat
El Miércoles, 6 de Mayo de 2009, Vikram Chhibber escribió:
> No. From the RFC 3891, it is clear that you can only replace early
> dialog which is initiated by the UA.
> In your scenario, how can you say it is attended-transfer when the
> transferor and
> transfer-target never had a conversation?
E
On Tue, May 5, 2009 at 9:41 PM, Vivek Batra
wrote:
> Hi Folks,
>
> I have one straight question may be I am not able to read between the words.
>
>
> As per RFC 3891 Section 3:
>
>
>
> If the Replaces header field matches an early dialog that was not
> initiated by this UA, it returns a 481 (Cal
Hi Folks,
I have one straight question may be I am not able to read between the words.
As per RFC 3891 Section 3:
If the Replaces header field matches an early dialog that was not
initiated by this UA, it returns a 481 (Call/Transaction Does Not
Exist) response to the new INVITE, and l
13 matches
Mail list logo
