Tele: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
 
(300 intermediate revisions by the same user not shown)
Line 1: Line 1:
<div style="color: navy;background-color: antiquewhite;><br><br>
<div style="color: navy;background-color: antiquewhite;><br><center>
<blockquote>
<span style="font-size: 22px;color: black;">Call Model</span> &mdash;
I define Ft as a conference call handling protocol similar to the one that has evolved with voice telephony since the late 19th Century. It is based on a canonical flow of the states below which will be the color of the primary button. There are manifold exceptions which the network and subscriber cooperatively manage:
<span style="font-size: 16px;color: black;" class=plainlinks> <html><a title='an older name for a slightly larger scope and line of development' href=https://eg.meansofproduction.biz/eg/index.php/Ft>DS VT</a></html> abstracts a backend provider, natively [https://jitsi.sameboat.network Jitsi].</span><br>Concise story of domain space [[:en:smart doorbell]].
<br><br>
</center>
<html><ol start=0>  
<center>
      <li>  <font size=1 color=black style="background-color: ivory;"> &nbsp; &nbsp;<b>ATTENTION &nbsp; </b> </font>  
<table style="border: solid;border-style: inset;border-width: thick;background-color: black;color: white;" width=70%>
        <blockquote>Ordinary ringer state, like a backlit doorbell, request for answer/attention default state if connected, not busy or other activity.
<tr style="background-color: white;color: navy;font-weight: 700;"><td align=center>Ordinal</td><td align=center>Color</td><td align=center>State</td><td align=center>Visibility</td><td width=150
        Causes UI changes in a context and device dependent manner. </blockquote>  
align=center>Enabled</td></tr>
        </li>
<caption style="font-weight: 700;background-color: white;color: navy;caption-side: bottom;">doorbell metaphor: button controls and tracks video conference call states</caption>
       <li> <font size=1 color=white style="background-color: maroon;"> &nbsp; <b>DOWN/OFFHOOK/REJECT</b>&nbsp; </font>  
<tr><td align=center width=5%>-1</td><td>White</td>  
         <blockquote>All subscribers are initially are in this state and may move to it by personal selection or involuntarily due to network events.</blockquote>
       <td width=75%><center><span style="color: black;background-color: white;font-weight: 700;font-size: 10px;"> &nbsp; OFFLINE  &nbsp; </span></center>  
    </li>
         <blockquote style="text-align:justify;">No subscriber context or caller device rejected. </blockquote>  
      <li> <font size=1 color=white style="background-color: black;"> &nbsp; &nbsp;<b>AFK/ASIDE/BUSY &nbsp; </b> </font>  
        </td><td align=center width=10%>Caller</td><td>No</td></tr>
         <blockquote>A subscriber controlled state which blocks calls until the subscriber double click toggles to READY. Single click same as ATTENTION. </blockquote>  
<tr><td align=center>0</td> <td>Cyan</td> <td><center><span style="color: black;background-color: cyan;font-weight: 700;font-size: 10px;"> &nbsp; ATTENTION &nbsp; </span></center>  
         </li>
         <blockquote style="text-align:justify;">Subscriber on hook state, like a backlit doorbell, ready to join or originate a call. Double click toggles offhook and single moves to LOOKUP/PAGE.</blockquote>  
      <li> <font size=1 color=white style="background-color: green;"> &nbsp; <b>ACCEPT/ANSWER/READY</b>&nbsp; </font>
         </td><td align=center>Subscriber</td><td>Yes</td></tr>
         <blockquote>A subscriber moves to this state after connecting to a call assuming no event, such as their or the
<tr><td align=center>1</td>  <td>Blue</td><td><center><span style="color: white;background-color: blue;font-weight: 700;font-size: 10px;"> &nbsp; LOOKUP/PAGE &nbsp; </span></center>
          network having set a different state preventing same. Blinking indicates incoming  call (slow) or conference (rapid).  
         <blockquote style="text-align:justify;">If no user or group callee is implicit, clicking prompts for the subscriber or group lookup text, which is then looked up. If the lookup finds an active call, the join processing for this Agent and call begin. If there is an implicit callee, they are rung up. If ring up attempt fails, returns to ATTENTION otherwise moves to IN CALL. Default on hook state for an non-subscribing caller. </blockquote>  
          Double click toggles to BUSY. Single click answers calls, view messages.</blockquote>
       </td><td align=center>Both</td><td>Yes</td></tr>
       </li>
<tr><td align=center>2</td>  <td>Yellow</td><td><center><span style="color: black;background-color: yellow;font-weight: 700;font-size: 10px;"> &nbsp; INCOMING &nbsp; </span></center>  
      <li>  <font size=1 color=white style="background-color: yellow; color: navy;"> &nbsp; <b>BUFF/WAIT</b>&nbsp; </font>  
         <blockquote style="text-align:justify;" >Indicates incoming events for the agent.  Blinks until callee dispatches state.
         <blockquote>A network controlled state which indicates incoming events for the subscriber. It is normal for some such events not to
          Single click moves the call to a holding state. While in the holding state information on the call is presented to the callee which can include a live feed of the caller. Another single click by callee connects the call. At any time a double click drops the call.</blockquote>  
        result in actual incoming as for example when the remote subscriber cancels a message before sending it. The button is inhibited if it is solidly this color rather than a ring on another color.</blockquote>  
       </td><td align=center>Subscr.</td><td>Yes</td></tr>
       </li>  
<tr><td align=center>3</td> <td>Green</td><td><center><span style="color: white;background-color: green;font-weight: 700;font-size: 10px;"> &nbsp; IN CALL &nbsp; </span></center>
      <li> <font size=1 color=white style="background-color: blue;"> &nbsp; <b>CALL/LOOKUP/PAGE </b>&nbsp; </font>
         <blockquote style="text-align:justify;" >Call active, blinks when additional callers join the call. Single click moves to BUSY. Double click ends call.</blockquote>
         <blockquote>A state in which the subscriber has initiated a call, or can lookup a remote subscriber or group. Entry/exit from/to ATTENTION or BUSY by menu or gesture depending on device. </blockquote>  
      </td><td align=center>Both</td><td>Yes</td></tr>
      </li>  
<tr><td align=center>4</td><td>Red</td><td><center><span style="color: white;background-color: maroon;font-weight: 700;font-size: 10px;"> &nbsp; AFK/ASIDE/BUSY &nbsp; </span></center>
  </ol>
        <blockquote style="text-align:justify;" >A subscriber controlled state indicating the user is in a dialog or momentarily off camera. Entered by swipe down, exited by swipe up, blinks while block active for subscriber solid for other callers. </blockquote>
  <blockquote>Visual cues, such as blinking, frame highlighring, fade-in/out indicate attention/opportunity or operation in progress.</blockquote>
        </td><td align=center>Both</td><td>Yes</td></tr>
The overall Ft GUI operates with elements such as the taskbar, main screen, and conferees array with elements in modal focus to constrain which subscriber pairs are involved and which gestures the subscriber has available. For example single click on a call state prompts for a subscriber lookup, whereas double click when paired with a selected subscriber initiates a call/page. Similary a device and state dependent gesture will determine the scope of an action, a single pair, the whole conference or a selected proper subgroup.  
<tr><td align=center>5</td><td>Black</td><td><center><span style="color: white;background-color: #636161;font-weight: 700;font-size: 10px;"> &nbsp; DOWN/OFFHOOK/REJECT &nbsp; </span></center>  
<br><br>
        <blockquote style="font-size:10px;font-weight:600;text-align:justify;">Agents may be Callers or Subscribers, both can initiate calls but only a Subscriber can receive them, owns a doorbell. Both start in this state and may enter it only as a result of network events. Clicking if enabled moves to ATTENTION or OFFLINE depending on entering state and network.</blockquote>
A distinguished subscriber in a conference call at any one time is the moderator, with overall control. A special case is the second joiner to a call after the initiator who is implicitly a co-moderator without the ability to transfer moderation (unless the user becomes moderator). Initially it is the initiator, the first caller but thereafter it may be transferred to any party to the call who will then have the following functions available:
      </td><td align=center>Both</td><td>Subscr.</td></tr>
<ol><li>Join another conference creating or enlarging a global conference.</li><li>Terminate the conference</li><li>Stream a service to a set of conferees, all or a group.</li><li>Mute, Call, or Disconnect any other conferee</li><li>Make the co-moderator an ordinary conferee.</li><li>Transfer moderation to another user. If the moderator disconnects from the call and goes OFFHOOK, without transferring moderation, the call/conference is automatically ended.</li>
  </table></center><br>
</ol>.<br>
Conferences may have asides of up to four subscribers and these may survive the conference call. A global conference is a special case of a general conference with limitations, e.g. asides and subgroups are limited to local conferences and there is no moderation distinct from that of the local conferences. The moderator of the first local conference in a global one can disconnect any local conference, but otherwise each local conference has the same limited access to the global one. The network itself is not a global conference.<br><br> <br>
</html>
</blockquote>
</div>
</div>

Latest revision as of 00:37, 22 October 2024


Call Model DS VT abstracts a backend provider, natively Jitsi.
Concise story of domain space en:smart doorbell.

OrdinalColorStateVisibilityEnabled
doorbell metaphor: button controls and tracks video conference call states
-1White
  OFFLINE  

No subscriber context or caller device rejected.

CallerNo
0 Cyan
  ATTENTION  

Subscriber on hook state, like a backlit doorbell, ready to join or originate a call. Double click toggles offhook and single moves to LOOKUP/PAGE.

SubscriberYes
1 Blue
  LOOKUP/PAGE  

If no user or group callee is implicit, clicking prompts for the subscriber or group lookup text, which is then looked up. If the lookup finds an active call, the join processing for this Agent and call begin. If there is an implicit callee, they are rung up. If ring up attempt fails, returns to ATTENTION otherwise moves to IN CALL. Default on hook state for an non-subscribing caller.

BothYes
2 Yellow
  INCOMING  

Indicates incoming events for the agent. Blinks until callee dispatches state. Single click moves the call to a holding state. While in the holding state information on the call is presented to the callee which can include a live feed of the caller. Another single click by callee connects the call. At any time a double click drops the call.

Subscr.Yes
3 Green
  IN CALL  

Call active, blinks when additional callers join the call. Single click moves to BUSY. Double click ends call.

BothYes
4Red
  AFK/ASIDE/BUSY  

A subscriber controlled state indicating the user is in a dialog or momentarily off camera. Entered by swipe down, exited by swipe up, blinks while block active for subscriber solid for other callers.

BothYes
5Black
  DOWN/OFFHOOK/REJECT  

Agents may be Callers or Subscribers, both can initiate calls but only a Subscriber can receive them, owns a doorbell. Both start in this state and may enter it only as a result of network events. Clicking if enabled moves to ATTENTION or OFFLINE depending on entering state and network.

BothSubscr.