Tele: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
(291 intermediate revisions by the same user not shown)
Line 1: Line 1:
<div style="color: navy;background-color: antiquewhite;>
<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>  
<center>
      <li> <font size=1 color=white style="background-color: maroon;"> &nbsp; <b>DOWN/OFFHOOK/REJECT</b>&nbsp; </font>  
<table style="border: solid;border-style: inset;border-width: thick;background-color: black;color: white;" width=70%>
         <blockquote>All subscribers are initially are in this state and may move to it by personal selection or involuntarily due to network events.</blockquote>
<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>
    </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: black;"> &nbsp; &nbsp;<b>AFK/BUSY</b> </font>  
<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>  
         <blockquote>A subscriber controlled state which blocks calls until the subscriber toggles to READY.</blockquote>  
         <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>
         </li>
      </td><td align=center>Both</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 width=5%>-1</td><td>White</td>
         <blockquote>A subscriber moves to this state after connecting assuming no event, such as their or the
      <td width=75%><center><span style="color: black;background-color: white;font-weight: 700;font-size: 10px;"> &nbsp; OFFLINE  &nbsp; </span></center>
          network having set a different state once at least one incoming message/call is active. Toggles to BUSY.</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: yellow; color: navy;"> &nbsp; <b>BUFF/WAIT</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 network controlled state which indicates incoming events for the subscriber. It is normal for some such events not to
         <blockquote>Ordinary ringer state, like a backlit doorbell, ready to join or originate a call.  Blinking indicates individual (slow) or group (rapid) incoming call.
        result in actual incoming as for example when the remote subscriber cancels a message before sending it.</blockquote>  
          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>  
       </li>  
         </td><td align=center>Subscriber</td><td>Yes</td></tr>
      <li> <font size=1 color=white style="background-color: blue;"> &nbsp; <b>CALL/LOOKUP/PAGE </b>&nbsp; </font>
<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>
         <blockquote>A state in which the subscriber can or has initiated a call, or can lookup a remote subscriber or group. </blockquote>  
         <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>  
      </li>  
       </td><td align=center>Caller</td><td>Yes</td></tr>
  </ol>
<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>  
  <blockquote>Visual cues, such as blinking, fade-in/out indicated attention/opportunity or operation in progress.</blockquote><br><br>
         <blockquote>Indicates incoming events for the agent. The control is inhibited if it is solidly this color .</blockquote>  
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.<br><br>
       </td><td align=center>Both</td><td>If blinking</td></tr>
A distinguished subscriber in a conference call at any one time is the moderator, with overall control.<br><br><br>
<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>
</html>
         <blockquote>Call active, blinks when additional callers join the call. Single click moves to BUSY. Double click ends call.</blockquote>
</blockquote>
      </td><td align=center>Both</td><td>Yes</td></tr>
<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>  
        <blockquote>A subscriber controlled state which blocks ATTENTION requests. Click toggles, blinks while block active. Caller sees briefly before moving to PAGE. </blockquote>
        </td><td align=center>Both</td><td>Yes</td></tr>
  </table></center><br>
</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"