Continuity Testing Call Flow (CCR/COT)
From TBwiki
(Difference between revisions)
Nicole Tan (Talk | contribs) m (moved Continuity Testing Callflow (CCR/COT) to Continuity Testing Call Flow (CCR/COT): Callflow -> Call Flow) |
Nicole Tan (Talk | contribs) |
||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Continuity tests are used to make sure that the SS7 ISUP interface | + | Continuity tests are used to test the speech or transmission path of SS7 circuits. It also make sure that the SS7 ISUP interface circuits (CIC) are aligned with the same physical links (E1/T1) on both end equipments. |
Toolpack version 2.7 allows users of the TMG to do ISUP Continuity Testing via 3 methods by CIC Group or individual CIC: | Toolpack version 2.7 allows users of the TMG to do ISUP Continuity Testing via 3 methods by CIC Group or individual CIC: | ||
== Incoming Continuity Testing Outside A Call == | == Incoming Continuity Testing Outside A Call == | ||
| − | This circuit testing occurs when one of the nodes wants to validate a currently idle circuit. | + | This circuit testing occurs when one of the nodes wants to validate a currently idle circuit. It is recommended that the switch first blocks the circuit to prevent calls to use the circuit during the testing. |
| − | It is recommended that the switch first blocks the circuit to prevent calls to use the circuit during the testing. | + | |
| − | + | ||
| − | + | ||
For ITU: | For ITU: | ||
<pre> | <pre> | ||
| − | Peer SP | + | Peer SP TMG |
| − | + | | | | |
| − | + | |---------- CCR ---------->| | |
| − | + | | | (timeslot loopback) | |
| − | + | |---------- Tone ----------\ | |
| − | + | |<-------------------------/ | |
| + | | | | ||
| + | |---------- REL ---------->| | ||
| + | |<--------- RLC -----------| | ||
</pre> | </pre> | ||
For ANSI: | For ANSI: | ||
<pre> | <pre> | ||
| − | Peer SP | + | Peer SP TMG |
| − | + | | | | |
| − | + | |---------- CCR ---------->| | |
| − | + | | | (timeslot loopback) | |
| − | + | |<--------- LPA -----------| | |
| − | + | | | | |
| − | + | |---------- Tone ----------\ | |
| + | |<-------------------------/ | ||
| + | | | | ||
| + | |---------- REL ---------->| | ||
| + | |<--------- RLC -----------| | ||
</pre> | </pre> | ||
| Line 32: | Line 36: | ||
This circuit testing occurs when the forward side (originating side) sets the ‘continuity test required’ field of the ‘nature of connection indicators’ IE into the IAM message. | This circuit testing occurs when the forward side (originating side) sets the ‘continuity test required’ field of the ‘nature of connection indicators’ IE into the IAM message. | ||
| − | + | Successful continuity check: | |
<pre> | <pre> | ||
| − | Peer SP | + | Peer SP TMG |
| − | + | | | | |
| − | + | |---------- IAM ---------->| 'continuity test required' | |
| − | + | | | | |
| − | COT | + | | | (timeslot loopback) |
| − | + | |---------- Tone ----------\ | |
| − | + | |<-------------------------/ | |
| − | + | | | | |
| − | + | |---------- COT ---------->| continuity check successful | |
| − | + | . . | |
| − | + | . . | |
| + | . . | ||
| + | |---------- REL ---------->| | ||
| + | |<--------- RLC -----------| | ||
| + | </pre> | ||
| + | |||
| + | Failed continuity check with retry from Peer SP: | ||
| + | <pre> | ||
| + | Peer SP TMG | ||
| + | | | | ||
| + | |---------- IAM ---------->| 'continuity test required' | ||
| + | | | | ||
| + | | | (timeslot loopback) | ||
| + | |---------- Tone ----------\ | ||
| + | |<-------------------------/ | ||
| + | | | | ||
| + | |---------- COT ---------->| continuity check failed | ||
| + | | | | ||
| + | Retry |---------- CCR ---------->| | ||
| + | | | (timeslot loopback) | ||
| + | |---------- Tone ----------\ | ||
| + | |<-------------------------/ | ||
| + | | | | ||
| + | |---------- COT ---------->| continuity check successful | ||
| + | . . | ||
| + | . . | ||
| + | . . | ||
| + | |---------- REL ---------->| | ||
| + | |<--------- RLC -----------| | ||
</pre> | </pre> | ||
| Line 50: | Line 82: | ||
Users of the TMG unit can generate out of call SS7 ISUP Continuity Tests via webportal easily. | Users of the TMG unit can generate out of call SS7 ISUP Continuity Tests via webportal easily. | ||
| − | |||
<pre> | <pre> | ||
| − | Peer SP | + | Peer SP TMG |
| − | + | | | | |
| − | + | |<--------- CCR ---------- | | |
| − | + | (timeslot | | | |
| − | + | loopback) | | | |
| − | + | /---------- Tone ----------| | |
| + | \------------------------->| ccr success or fail | ||
| + | | | | ||
| + | |<--------- REL -----------| | ||
| + | |---------- RLC ---------->| | ||
</pre> | </pre> | ||
== Configuration == | == Configuration == | ||
*[[Outgoing COT testing|Web Portal v2.7: Outgoing Continuity Testing]] | *[[Outgoing COT testing|Web Portal v2.7: Outgoing Continuity Testing]] | ||
| + | |||
| + | == External Sources == | ||
| + | *[ftp://109.167.129.114/doc/ITU-T/Q/Q0784e.pdf Q.784-Isup Basic Call Test Specification] | ||
Latest revision as of 08:43, 25 April 2014
Continuity tests are used to test the speech or transmission path of SS7 circuits. It also make sure that the SS7 ISUP interface circuits (CIC) are aligned with the same physical links (E1/T1) on both end equipments. Toolpack version 2.7 allows users of the TMG to do ISUP Continuity Testing via 3 methods by CIC Group or individual CIC:
Contents |
Incoming Continuity Testing Outside A Call
This circuit testing occurs when one of the nodes wants to validate a currently idle circuit. It is recommended that the switch first blocks the circuit to prevent calls to use the circuit during the testing.
For ITU:
Peer SP TMG
| |
|---------- CCR ---------->|
| | (timeslot loopback)
|---------- Tone ----------\
|<-------------------------/
| |
|---------- REL ---------->|
|<--------- RLC -----------|
For ANSI:
Peer SP TMG
| |
|---------- CCR ---------->|
| | (timeslot loopback)
|<--------- LPA -----------|
| |
|---------- Tone ----------\
|<-------------------------/
| |
|---------- REL ---------->|
|<--------- RLC -----------|
Incoming Continuity Testing Within A Call
This circuit testing occurs when the forward side (originating side) sets the ‘continuity test required’ field of the ‘nature of connection indicators’ IE into the IAM message.
Successful continuity check:
Peer SP TMG
| |
|---------- IAM ---------->| 'continuity test required'
| |
| | (timeslot loopback)
|---------- Tone ----------\
|<-------------------------/
| |
|---------- COT ---------->| continuity check successful
. .
. .
. .
|---------- REL ---------->|
|<--------- RLC -----------|
Failed continuity check with retry from Peer SP:
Peer SP TMG
| |
|---------- IAM ---------->| 'continuity test required'
| |
| | (timeslot loopback)
|---------- Tone ----------\
|<-------------------------/
| |
|---------- COT ---------->| continuity check failed
| |
Retry |---------- CCR ---------->|
| | (timeslot loopback)
|---------- Tone ----------\
|<-------------------------/
| |
|---------- COT ---------->| continuity check successful
. .
. .
. .
|---------- REL ---------->|
|<--------- RLC -----------|
Outgoing Continuity Testing
Users of the TMG unit can generate out of call SS7 ISUP Continuity Tests via webportal easily.
Peer SP TMG
| |
|<--------- CCR ---------- |
(timeslot | |
loopback) | |
/---------- Tone ----------|
\------------------------->| ccr success or fail
| |
|<--------- REL -----------|
|---------- RLC ---------->|
