Difference between revisions of "Tele"

From Cibernética Americana
 
(196 intermediate revisions by the same user not shown)
Line 1: Line 1:
<div style="color: navy;background-color: antiquewhite;><br><html><center>
+
<div style="color: navy;background-color: antiquewhite;><br><center>
<blockquote>
+
<span style="font-size: 22px;color: black;">Tele Doorbell</span> &mdash;
The below will shortly be revised for the integration of Jitsi with DS.  
+
<span style="font-size: 16px;color: black;"> <span class=plainlinks>[https://eg.meansofproduction.biz/index.php/Ft Ft]</span> join point for Guacamole, Jitsi, and Zoom in a DS context and as deployed to the sameboat nodes.</span><br>Concise story of the sameboat <span class=plainlinks>[https://sameboat.live/drucall 'doorbell']</span>, a [[redvant]] applet &int; &part; MCS / &part; DCP DS.
</blockquote>
+
</center>
<a title='Real time FLASH FRANKENSTEEN that works, HTML5 version WIP at domain base. Please use Whatsapp for the 619 phone number' href=https://doorbell.meansofproduction.biz/old.html><span style="font-size: 16px; font-weight: 900; background-color: black;"> &nbsp; Legacy Prototype &nbsp; </span></a></center></html>
+
<center>
<blockquote>
+
<table style="border: solid;border-style: inset;border-width: thick;background-color: black;color: white;" width=70%>
The current intent/method of integration is that the existing legend bar will normally just be the doorbell with a flap or tip for expansion to display the full bar.
+
<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>Control</td><td align=center>Visibility</td></tr>
<br><br>
+
<caption style="font-weight: 700;background-color: white;color: navy;caption-side: bottom;">doorbell metaphor: ringer controls and tracks video conference call states</caption>
<html><ol start=0>  
+
<tr><td align=center width=5%>-1</td><td>White</td>
      <li> <font size=1 color=black style="background-color: ivory;"> &nbsp; &nbsp;<b>ATTENTION &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>Ordinary ringer state, like a backlit doorbell, ready to accept or originate call.  Blinking indicates incoming  call (slow) or conference (rapid).  
+
        <blockquote>Disconnected state, no subscriber or subscriber device not authenticated. </blockquote>  
           Double click toggles to BUSY. Single click answers moving to IN CALL.</blockquote>  
+
        </td><td>Ringer</td><td align=center width=10%>Caller</td></tr>
         </li>
+
<tr><td align=center>0</td> <td>Ivory</td> <td><center><span style="color: black;background-color: ivory;font-weight: 700;font-size: 10px;"> &nbsp; ATTENTION &nbsp; </span></center>  
      <li> <font size=1 color=white style="background-color: black;"> &nbsp; <b>DOWN/OFFHOOK/REJECT</b>&nbsp; </font>  
+
         <blockquote>Ordinary ringer state, like a backlit doorbell, ready to accept or originate call.  Blinking indicates ring (slow) or busy (rapid).  
         <blockquote>All subscribers start in this state and may move to it by personal selection or involuntarily due to network events.</blockquote>
+
           Single click rings (caller) or answers (subscriber) moving to IN CALL.</blockquote>  
    </li>
+
         </td><td>Ringer</td><td align=center>Both</td></tr>
      <li>  <font size=1 color=white style="background-color: maroon;"> &nbsp; &nbsp;<b>AFK/ASIDE/BUSY &nbsp; </b> </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 subscriber controlled state which blocks ATTENTION requests until the subscriber click toggles to ATTENTION or double clicks to OFFHOOK.   </blockquote>  
+
         <blockquote>Agent has initiated a call, or lookup of a remote subscriber or group. Submits the subscriber lookup text. Lookup is the action when no
        </li>
+
subscriber is selected and page is the action if one is (ringer calls selection). </blockquote>  
      <li> <font size=1 color=white style="background-color: green;"> &nbsp; <b>IN CALL</b>&nbsp; </font>
+
      </td><td>Aux 2</td><td align=center>Both</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>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>  
          network having set a different state preventing same.</blockquote>
+
         <blockquote>Indicates incoming events for the agent. The control is inhibited if it is solidly this color .</blockquote>  
       </li>
+
      </td><td>Ringer</td> <td align=center>Both</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>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>
         <blockquote>A network controlled state which indicates incoming events for the subscriber. It is normal for some such events not to
+
         <blockquote>Call active, blinks when additional callers join 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>Ringer</td><td align=center>Both</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>  
      <li> <font size=1 color=white style="background-color: blue;"> &nbsp; <b>CALL/LOOKUP/PAGE </b>&nbsp; </font>
+
         <blockquote>A subscriber controlled state which blocks ATTENTION requests. Click toggles, blinks while block active.   </blockquote>  
         <blockquote>A state in which the subscriber has initiated a call, or lookup of a remote subscriber or group. Entry/exit from/to ATTENTION or BUSY by menu or gesture depending on device. </blockquote>
+
        </td><td>Aux 1</td><td align=center>Subscriber</td></tr>
      </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>  
  </ol>
+
         <blockquote style="font-size:10px;font-weight:600;">Agents start in this state, may move to it by personal selection or involuntarily due to network events, or a failure to transition to ATTENTION, the next state goal. Double clicking in response to incoming call rejects the call and the subscribers ringer is briefly in this state to acknowledge the drop. Subscriber double clicking when there's no call toggles offhook. Double clicking during a call disconnects it with brief acknowledgement in this color before returning to ATTENTION.</blockquote>
  <blockquote>Visual cues, such as blinking, frame highlighring, fade-in/out indicate attention/opportunity or operation in progress.</blockquote>
+
      </td><td>Ringer</td><td align=center>Both</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.
+
  </table></center>
<br><br>
+
<blockquote><center>
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:
+
<blockquote style="font-weight: 500;">Obviates login/profile blurb, if device authenticated device, SPA tries to run FSA, which if it connects to DCMS&gt;, subscriber dial/lookup/passphrase multiselect and Aux 2 button show and Ringer is not white.<br>On a subscribers profile, viewed by others, the subscriber is the callee so no lookup is present. </blockquote></center>
<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>
+
</blockquote><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 17:28, 21 March 2021


Tele Doorbell Ft join point for Guacamole, Jitsi, and Zoom in a DS context and as deployed to the sameboat nodes.
Concise story of the sameboat 'doorbell', a redvant applet ∫ ∂ MCS / ∂ DCP DS.

OrdinalColorStateControlVisibility
doorbell metaphor: ringer controls and tracks video conference call states
-1White
  OFFLINE  

Disconnected state, no subscriber or subscriber device not authenticated.

RingerCaller
0 Ivory
  ATTENTION  

Ordinary ringer state, like a backlit doorbell, ready to accept or originate call. Blinking indicates ring (slow) or busy (rapid). Single click rings (caller) or answers (subscriber) moving to IN CALL.

RingerBoth
1 Blue
  LOOKUP/PAGE  

Agent has initiated a call, or lookup of a remote subscriber or group. Submits the subscriber lookup text. Lookup is the action when no subscriber is selected and page is the action if one is (ringer calls selection).

Aux 2Both
2 Yellow
  BUFF/WAIT  

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

Ringer Both
3 Green
  IN CALL  

Call active, blinks when additional callers join the call.

RingerBoth
4Red
  AFK/ASIDE/BUSY  

A subscriber controlled state which blocks ATTENTION requests. Click toggles, blinks while block active.

Aux 1Subscriber
5Black
  DOWN/OFFHOOK/REJECT  

Agents start in this state, may move to it by personal selection or involuntarily due to network events, or a failure to transition to ATTENTION, the next state goal. Double clicking in response to incoming call rejects the call and the subscribers ringer is briefly in this state to acknowledge the drop. Subscriber double clicking when there's no call toggles offhook. Double clicking during a call disconnects it with brief acknowledgement in this color before returning to ATTENTION.

RingerBoth

Obviates login/profile blurb, if device authenticated device, SPA tries to run FSA, which if it connects to DCMS>, subscriber dial/lookup/passphrase multiselect and Aux 2 button show and Ringer is not white.
On a subscribers profile, viewed by others, the subscriber is the callee so no lookup is present.