Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 1.4.1
-
Component/s: None
-
Labels:None
Description
Implement conferencing feature. There are two modes:
1) Start new conference call
2) Turn an existing two-way call into a conference call by inviting one or more new people in.
To implement #2
1. dynamically create a conference room
2. to an action: redirect to move the existing people to the conference room
3. Find a free Zap device
4. finally originate other people to the conference room using the zap device:
Action: Originate
Channel: zap/g1/myphonenumber
Application: MeetMe
Data: confnum,pinnnum
Activity
Updated the issue to be more about generic conferencing support. In the admin console, I would imagine the following settings:
Meet-me extension [ 4222 ]
Use conference room numbers between [ 9500 ] and [ 9600 ]
Conference pins:
( ) Will be andomly generated
Will always use the value [ 666 ]
Will always use the value [ 666 ]
I don't think this is actually the definition of attended transfer. Here are some definitions I found of different transfer types:
Blind Transfer - Alice is in a conversation with Bob. Alice asks
Bob to contact Carol, but makes no attempt to contact Craol
independently. In many implementations, Alice does not verify Bob's
success or failure in contacting Carol.
Attended Transfer - The transferring party establishes a session
with the transfer target before completing the transfer.
Consultative transfer - the transferring party establishes a session
with the target and mixes both sessions together so that all three
parties can participate, then disconnects leaving the transferee and
transfer target with an active session.
Conference Call - Three or more active, visible participants in the
same conversation space.