Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353038 - No way to specify MaxTime attribute for the Transfer block
Summary: No way to specify MaxTime attribute for the Transfer block
Status: NEW
Alias: None
Product: VTP
Classification: Technology
Component: editors (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Terran Gilman CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-25 15:40 EDT by Randy Childers CLA
Modified: 2011-08-03 02:47 EDT (History)
0 users

See Also:

Attachments
maxTime and duration variable patch (33.48 KB, patch)
2011-08-03 02:47 EDT, Ehsan Afzali CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Randy Childers CLA 2011-07-25 15:40:20 EDT 
This needs to be added to the UI, to the data storage subsystem, and also to the runtime.
Comment 1 Ehsan Afzali CLA 2011-08-03 02:47:30 EDT 
Created attachment 200774 [details]
maxTime and duration variable patch

I've added a maxTime property for Advanced Transfer Module and added the UI elements.
And also acoording to this example:
http://www.w3.org/TR/voicexml20/#dml2.3.7.4
I've added 'Continue' exit point, because 'connection.disconnect.transfer' (The 'Call Transfered' Exit) will raise only in blind transfer not bridge transfer and in this case after that the transfer completes interpreter will continue the form,
http://www.w3.org/TR/voicexml20/#dml2.3.7.
I've also added BridgeDuration variable to 'continue' exit point that will represents the duration of transfered call.