Tele: Difference between revisions
No edit summary |
No edit summary |
||
| Line 18: | Line 18: | ||
</li> | </li> | ||
<li> <font size=1 color=white style="background-color: blue;"> <b>CALL/PAGE </b> </font> | <li> <font size=1 color=white style="background-color: blue;"> <b>CALL/PAGE </b> </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 14: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:
- DOWN/OFFHOOK/REJECT
All subscribers are initially are in this state and may move to it by personal or network events.
- AFK/BUSY
A subscriber controlled state which blocks calls until the subscriber sets READY.
- 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.
- BUFF/WAIT
A network controlled state which indicates incoming events for the subscriber.
- 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.
