Difference between revisions of "Tele"

From Cibernética Americana
Line 18: Line 18:
 
       </li>  
 
       </li>  
 
       <li>  <font size=1 color=white style="background-color: blue;"> &nbsp; <b>CALL/PAGE </b>&nbsp; </font>
 
       <li>  <font size=1 color=white style="background-color: blue;"> &nbsp; <b>CALL/PAGE </b>&nbsp; </font>
         <blockquote>A state in which the subscriber can or has initiated a call.</blockquote>  
+
         <blockquote>A state in which the subscriber can or has initiated a call. </blockquote>  
 
       </li>  
 
       </li>  
 
   </ol>
 
   </ol>
 +
  <blockquote>Visual cues, such as blinking, fade-in/out indicated attention/opportunity or operation in progress.</blockquote>
 
</html>
 
</html>
 
</blockquote>
 
</blockquote>
 
</div>
 
</div>

Revision as of 22:03, 12 May 2018

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 these states with manifold exceptions:

  1.   DOWN/OFFHOOK/REJECT 

    All subscribers are initially are in this state and may move to it by personal or network events.

  2.    AFK/BUSY

    A subscriber controlled state which blocks calls until the subscriber sets READY.

  3.   ACCEPT/ANSWER/READY 

    A subscriber moves to this state after connecting assuming no event, such as their or the network having set a different state.

  4.   BUFF/WAIT 

    A network controlled state which indicates incoming events for the subscriber.

  5.   CALL/PAGE  

    A state in which the subscriber can or has initiated a call.

Visual cues, such as blinking, fade-in/out indicated attention/opportunity or operation in progress.