MTP2:Proving Emergency - Revision history

Ktrueman: clean up

2009-09-02T13:42:08Z

clean up

Cboulanger at 02:52, 2 September 2009

2009-09-02T02:52:31Z

Ktrueman: initial content

2009-08-14T20:20:27Z

initial content

New page

NEED DESCRIPTION OF WHAT THIS PARAMETER REPRESENTS.

Emergency proving period timer (the same as TTC JT-Q.703 verification timer).

The typical value is 500 milliseconds (0.5 seconds) for ITU and 600 milliseconds (0.6 seconds) for ANSI.

[[Category:Needs revising]]

← Older revision		Revision as of 13:42, 2 September 2009
Line 1:		Line 1:
−	Before an MTP2 link can be considered as active, both sides of the connection needs to go through an handshake to ensure ~~about~~ the ready state of each peer and to test the quality of the physical transport layer (e.g. the [[timeslot]](s)). ~~The~~ handshaking involves different [[MSU]] exchanged between both MTP2 layers. Two different handshaking are available for an MTP2 link: normal and emergency. In both cases, the MTP2 link is considered activated if no errors are detected during the proving period. The "emergency" mode is used to test the link minimally and to bring it up as ~~quick~~ as possible. Therefore, it has the smallest proving period timer. The typical value is 500 milliseconds (0.5 seconds) for ITU and 600 milliseconds (0.6 seconds) for ANSI.	+	Before an MTP2 link can be considered as active, both sides of the connection needs to go through a handshake to ensure the ready state of each peer and to test the quality of the physical transport layer (e.g., the [[timeslot]](s)). This handshaking action involves different [[MSU]] exchanged between both MTP2 layers.
		+
		+
		+	Two different handshaking methods are available for an MTP2 link: normal and emergency. In both cases, the MTP2 link is considered activated if no errors are detected during the proving period. The "emergency" mode is used to test the link minimally and to bring it up as quickly as possible. Therefore, it has the smallest proving period timer. The typical value is 500 milliseconds (0.5 seconds) for ITU and 600 milliseconds (0.6 seconds) for ANSI.

@@ Line 1: / Line 1: @@
-NEED DESCRIPTION OF WHAT THIS PARAMETER REPRESENTS.
+Before an MTP2 link can be considered as active, both sides of the connection needs to go through an handshake to ensure about the ready state of each peer and to test the quality of the physical transport layer (e.g. the [[timeslot]](s)).  The handshaking involves different [[MSU]] exchanged between both MTP2 layers.  Two different handshaking are available for an MTP2 link: normal and emergency.   In both cases, the MTP2 link is considered activated if no errors are detected during the proving period.  The "emergency" mode is used to test the link minimally and to bring it up as quick as possible.  Therefore, it has the smallest proving period timer.  The typical value is 500 milliseconds (0.5 seconds) for ITU and 600 milliseconds (0.6 seconds) for ANSI.
-−
-Emergency proving period timer (the same as TTC JT-Q.703 verification timer).
-−
-−
 The typical value is 500 milliseconds (0.5 seconds) for ITU and 600 milliseconds (0.6 seconds) for ANSI.
-−
-−
-[[Category:Needs revising]]