Tele: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
(260 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;">Tele Doorbell</span> &mdash;
Ft defines a 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;"> <span class=plainlinks>[https://eg.meansofproduction.biz/eg/index.php/Ft Ft]</span> videotelephony and desktop sharing in a DS context with abstraction over the backend provider which defaults to Jitsi.</span><br>Concise story of sameboat [[: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 align=center>Enabled</td></tr>
        Makes menu, gestures available depending on device. </blockquote>  
<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>
<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>  
      <li> <font size=1 color=white style="background-color: maroon;"> &nbsp; <b>DOWN/OFFHOOK/REJECT</b>&nbsp; </font>  
         <blockquote style="font-size:10px;font-weight:600;">Agents may be Callers or Subscribers, both can initiate calls but only a Subscriber can receive them, has a doorbell. Both start in this state and may enter it as a result of network events. Double clicking in response to incoming call rejects the call and the subscribers ringer is briefly in this state to acknowledge the drop.  Double clicking during a call disconnects it and while that is being confirmed, the control is this color before returning to ATTENTION.</blockquote>
         <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><td align=center>Both</td><td>No</td></tr>
    </li>
<tr><td align=center width=5%>-1</td><td>White</td>
      <li> <font size=1 color=white style="background-color: black;"> &nbsp; &nbsp;<b>AFK/ASIDE/BUSY &nbsp; </b> </font>  
      <td width=75%><center><span style="color: black;background-color: white;font-weight: 700;font-size: 10px;"> &nbsp; OFFLINE  &nbsp; </span></center>  
         <blockquote>A subscriber controlled state which blocks calls until the subscriber double click toggles to READY. Single click same as ATTENTION. </blockquote>  
         <blockquote>No subscriber context or caller device rejected. </blockquote>  
         </li>
         </td><td align=center width=10%>Caller</td><td>No</td></tr>
      <li> <font size=1 color=white style="background-color: green;"> &nbsp; <b>ACCEPT/ANSWER/READY</b>&nbsp; </font>
<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>  
         <blockquote>A subscriber moves to this state after connecting to a call assuming no event, such as their or the
         <blockquote>Ordinary ringer state, like a backlit doorbell, ready to join or originate a call. Blinking indicates individual (slow) or group (rapid) incoming call.  
          network having set a different state preventing same. Blinking indicates incoming  call (slow) or conference (rapid).  
           Single click answers rings moving to IN CALL. If  ring initiated without a selected/defaulted subscriber, moves to LOOKUP/PAGE. Subscriber double clicking when there's no call toggles offhook. Long click moves to LOOKUP/PAGE.</blockquote>  
           Double click toggles to BUSY. Single click answers calls, view messages.</blockquote>
        </td><td align=center>Subscriber</td><td>Yes</td></tr>
      </li>
<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>
      <li> <font size=1 color=white style="background-color: yellow; color: navy;"> &nbsp; <b>BUFF/WAIT</b>&nbsp; </font>  
         <blockquote>If there is no selected subscriber to connect to, 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 a selected subscriber, they are rung up. Otherwise the control returns to this state for caller or to ATTENTION for subscriber. </blockquote>  
         <blockquote>A network controlled state which indicates incoming events for the subscriber. It is normal for some such events not to
       </td><td align=center>Caller</td><td>Yes</td></tr>
        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>  
<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; BUFF/WAIT &nbsp; </span></center>  
       </li>  
         <blockquote>Indicates incoming events for the agent. The control is inhibited if it is solidly this color .</blockquote>  
      <li>  <font size=1 color=white style="background-color: blue;"> &nbsp; <b>CALL/LOOKUP/PAGE </b>&nbsp; </font>
      </td><td align=center>Both</td><td>If blinking</td></tr>
         <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>  
<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>  
        <blockquote>Call active, blinks when additional callers join the call. Single click moves to BUSY. Double click ends call.</blockquote>
  </ol>
      </td><td align=center>Both</td><td>Yes</td></tr>
  <blockquote>Visual cues, such as blinking, frame highlighring, fade-in/out indicate attention/opportunity or operation in progress.</blockquote>
<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>  
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.
        <blockquote>A subscriber controlled state which blocks ATTENTION requests. Click toggles, blinks while block active. Caller sees briefly before moving to PAGE. </blockquote>  
<br><br>
        </td><td align=center>Both</td><td>Yes</td></tr>
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:
  </table></center><br>
<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>
</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>

Revision as of 10:08, 11 November 2022


Tele Doorbell — Ft videotelephony and desktop sharing in a DS context with abstraction over the backend provider which defaults to Jitsi.
Concise story of sameboat en:smart doorbell.

OrdinalColorStateVisibilityEnabled
doorbell metaphor: button controls and tracks video conference call states
5Black
  DOWN/OFFHOOK/REJECT  

Agents may be Callers or Subscribers, both can initiate calls but only a Subscriber can receive them, has a doorbell. Both start in this state and may enter it as a result of network events. Double clicking in response to incoming call rejects the call and the subscribers ringer is briefly in this state to acknowledge the drop. Double clicking during a call disconnects it and while that is being confirmed, the control is this color before returning to ATTENTION.

BothNo
-1White
  OFFLINE  

No subscriber context or caller device rejected.

CallerNo
0 Cyan
  ATTENTION  

Ordinary ringer state, like a backlit doorbell, ready to join or originate a call. Blinking indicates individual (slow) or group (rapid) incoming call. Single click answers rings moving to IN CALL. If ring initiated without a selected/defaulted subscriber, moves to LOOKUP/PAGE. Subscriber double clicking when there's no call toggles offhook. Long click moves to LOOKUP/PAGE.

SubscriberYes
1 Blue
  LOOKUP/PAGE  

If there is no selected subscriber to connect to, 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 a selected subscriber, they are rung up. Otherwise the control returns to this state for caller or to ATTENTION for subscriber.

CallerYes
2 Yellow
  BUFF/WAIT  

Indicates incoming events for the agent. The control is inhibited if it is solidly this color .

BothIf blinking
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 which blocks ATTENTION requests. Click toggles, blinks while block active. Caller sees briefly before moving to PAGE.

BothYes

Retrieved from "https://eg.meansofproduction.biz/eg/index.php?title=Tele&oldid=20439"