Tele: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
← Older edit
No edit summary
No edit summary
 
(153 intermediate revisions by the same user not shown)
Line 1: Line 1:
<div style="color: navy;background-color: antiquewhite;><br><center>
<div style="color: navy;background-color: antiquewhite;><br><center>
<span style="font-size: 22px;color: black;">Tele Doorbell</span><br>
<span style="font-size: 22px;color: black;">Call Model</span> &mdash;
<span style="font-size: 16px;color: black;">join point for Ft aspect of domain space deployed to the communal networks</span><br>Concise story of the [[Ft]] 'doorbell', a [[redvant]] applet &int; &part; {Bitlbee, Jitsi, Synapse} &part; SB/DS.
<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]].
</center>
</center>
<center>
<center>
<table style="border: solid;border-style: inset;border-width: thick;background-color: black;color: white;" width=70%>
<table style="border: solid;border-style: inset;border-width: thick;background-color: black;color: white;" width=70%>
<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>Control</td><td align=center>Visibility</td></tr>
<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
<caption style="font-weight: 700;background-color: white;color: navy;caption-side: bottom;">Doorbell metaphor: button color tracks network call states</caption>
align=center>Enabled</td></tr>
<caption style="font-weight: 700;background-color: white;color: navy;caption-side: bottom;">doorbell metaphor: button controls and tracks video conference call states</caption>
<tr><td align=center width=5%>-1</td><td>White</td>  
<tr><td align=center width=5%>-1</td><td>White</td>  
       <td width=75%> <font size=1 color=black style="background-color: white;"> &nbsp; &nbsp;<b>OFFLINE &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>Disconnected state, no subscriber or subscriber not Ft authenticated. </blockquote>  
         <blockquote style="text-align:justify;">No subscriber context or caller device rejected. </blockquote>  
         </td><td>Ringer</td><td align=center width=10%>Caller</td></tr>
         </td><td align=center width=10%>Caller</td><td>No</td></tr>
<tr><td align=center>0</td> <td>Ivory</td> <td><font size=1 color=black style="background-color: ivory;"> &nbsp; &nbsp;<b>ATTENTION &nbsp; </b> </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>Ordinary ringer state, like a backlit doorbell, ready to accept or originate call. Blinking indicates incoming  call (slow) or conference (rapid).
         <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>  
          Double click toggles to BUSY. Single click answers moving to IN CALL.</blockquote>  
         </td><td align=center>Subscriber</td><td>Yes</td></tr>
         </td><td>Ringer</td><td align=center>Caller</td></tr>
<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>
<tr><td align=center>1</td><td>Black</td><td> <font size=1 color=white style="background-color: black;"> &nbsp; <b>DOWN/OFFHOOK/REJECT</b>&nbsp; </font>  
         <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>  
         <blockquote>Agents join the network in this state and may move to it by personal selection or involuntarily due to network events. Single click moves to ATTENTION, double
      </td><td align=center>Both</td><td>Yes</td></tr>
        focuses CALL/PAGE input and moved to that state.</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; INCOMING &nbsp; </span></center>  
      </td><td>Ringer</td><td align=center>Subscriber</td></tr>
         <blockquote style="text-align:justify;" >Indicates incoming events for the agent.  Blinks until callee dispatches state.
<tr><td align=center>2</td>   <td>Red</td>   <td> <font size=1 color=white style="background-color: maroon;"> &nbsp; &nbsp;<b>AFK/ASIDE/BUSY &nbsp; </b> </font>  
          Single click moves the call to a holding state. While in this state information on the call may presented to the callee, indicated by a symbol and retrieved in a popup when the symbol is being displayed, 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>  
         <blockquote>A subscriber controlled state which blocks ATTENTION requests until an agent click toggles to ATTENTION/IN-CALL or double clicks to OFFHOOK.   </blockquote>  
      </td><td align=center>Subscr.</td><td>Yes</td></tr>
        </td><td>Aux 1</td><td align=center>Both</td></tr>
<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>
<tr><td align=center>3</td> <td>Green</td>     <td> <font size=1 color=white style="background-color: green;"> &nbsp; <b>IN CALL</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 agent moves to this state after connecting to a call assuming no event, such as their or the
       </td><td align=center>Both</td><td>Yes</td></tr>
          network having set a different state preventing same.</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>  
       </td><td>Ringer</td><td align=center>Both</td></tr>
         <blockquote style="text-align:justify;" >A subscriber controlled state indicating the user is in a call and momentarily unavailable. </blockquote>  
<tr><td align=center>4</td> <td>Yellow</td>   <td> <font size=1 color=white style="background-color: yellow; color: navy;"> &nbsp; <b>BUFF/WAIT</b>&nbsp; </font>  
        </td><td align=center>Caller</td><td>Yes</td></tr>
         <blockquote>A network controlled state which indicates incoming events for the agent. It is normal for some such events not to
<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>  
        result in actual incoming as for example when the remote agent cancels a message before sending it. The control is inhibited if it is solidly this color .</blockquote>  
        <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 as a result of network events. Clicking if enabled moves to ATTENTION or OFFLINE depending on entering state and network.</blockquote>
      </td><td>Ringer</td> <td align=center>Both</td></tr>
      </td><td align=center>Both</td><td>Subscr.</td></tr>
<tr><td align=center>5</td> <td>Blue</td>   <td> <font size=1 color=white style="background-color: blue;"> &nbsp; <b>CALL/LOOKUP/PAGE </b>&nbsp; </font>
  </table></center><br>
        <blockquote>A state in which the agent has initiated a call, or lookup of a remote subscriber or group. Entered as a result of data entry in
        UI and subsequent network events determine which state results. </blockquote>
      </td><td>Aux 1</td><td align=center>Caller</td></tr>
  </table></center>
<blockquote><center>
<blockquote style="font-weight: 500;">
The designed default is collapsed with an expand tab/flap, draggable and when connected the doorbell illumination will track the call state.<br>Obviates login/profile profile blurb for SPA, if client is authenticated device, auxiliary buttons, subscriber dial/lookup (or Jitsi meet passphrase) text box show and button is not white.</blockquote></center>
</blockquote>
<blockquote>Visual cues would need currently unaffordable modifications
to generalized sense modalities for accessibility but down the road ... . The system itself is an integration of various of my infrastructures with a derived jigasi client, videobridge server, and as many of the jitsi tools as are useful, which sfaik is all of them.</blockquote>
<blockquote>
The overall Ft GUI operates with elements such as the taskbar, main screen, and conferees array with elements in jicofo 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.  
<br><br>
A distinguished agent 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:
<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 subscribing agents 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>
</blockquote>
</div>
</div>
Retrieved from "https://eg.meansofproduction.biz/eg/index.php/Tele"