MTP2:Timers
From TBwiki
(Difference between revisions)
(clean up) |
Cboulanger (Talk | contribs) |
||
| (One intermediate revision by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | A total of 6 timers can be set as part of the common link configuration process. They are as follows (with definitions): | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| Line 30: | Line 24: | ||
| − | [[ | + | === Screenshot === |
| + | The following screenshot shows the fields for configuring timers in the MTP2 link configuration process. | ||
| + | |||
| + | |||
| + | [[Image:MTP2-link-configuration-timers.jpg|500px| ]] | ||
Latest revision as of 21:38, 1 September 2009
A total of 6 timers can be set as part of the common link configuration process. They are as follows (with definitions):
| Timer | Description |
|---|---|
| T1 Timer | Alignment ready timer (the same as TTC JT-Q.703 remote verification in progress timer). Typical value is 40000 milliseconds (40 seconds) for ITU and 13000 milliseconds (13 seconds) for ANSI. |
| T2 Timer | Not aligned timer (the same as TTC JT-Q.703 wait for remote startup in progress timer). Typical value is 5000 milliseconds (5 seconds) for ITU and 11800 milliseconds (11.8 seconds) for ANSI. |
| T3 Timer | Aligned timer (the same as TTC JT-Q.703 initialization in progress timer). Typical value is 1500 milliseconds (1.5 seconds) for ITU and 11800 milliseconds (11.8 seconds) for ANSI. |
| T5 Timer | Sending SIB timer. Typical value is 100 milliseconds (0.1 second). |
| T6 Timer | Remote congestion timer. Typical value is 3000 milliseconds (3 seconds). |
| T7 Timer | Excessive delay of acknowledgment timer. Typical value is 1000 milliseconds (1 second). |
NOTE: For all timers, a value of '0' is not permitted. Also, please note that there is no T4 Timer.
Screenshot
The following screenshot shows the fields for configuring timers in the MTP2 link configuration process.
