Change request to <transfer/> tag

Dear W3C Committee.. (Probably  late fore 2.0 but for 2.1 probably)

Case 1:

I would like to ask you a question about bridge transfer that terminates
with originating caller hang-up. Now the specification states that the event
telephone.disconnect.hangup is thrown when hang-up occurs and field item
does not get filled. As stated in chapter 2.3.7.2.2. 

Record (someone probably thought voicemail in here) is different; It is
stated that the record field item gets filled if something was recorded in
case of hang-up. 

To make it more clear to application developer the <transfer/> should not
differentiate form <record/> it should be filled if transfer took place and
the call was terminated with originating caller hang-up. So the Value of
form item variable should be filled with "caller_hangup" and the appropriate
field items should be filled too. This makes it possible to obtain call
information for logging, billing etc. I think that this is very important
cause platform provider call logs are rarely available to application
provider.  So the field gets filled and event "telephone.disconnect.hangup"
is thrown. This makes sense to me..

Case 2:

Somewhat I propose here little different approach for FIA in these special
cases for "collection of event and field information at the same time".
Firstly the FIA could work so the first the appropriate field items get
filled and "just_filled" list is managed as usual. After; this before
evaluating the need of processing any <filled/> elements , the event thrown
gets processed and if it does not cause any transition the appropriate
<filled> elements gets called. I found this very useful and I can give you
some examples if needed.

Ill try to post our IR asap after the statements are checked my our
marketing etc. 

- Teemu

Received on Tuesday, 10 February 2004 08:23:39 UTC