Continuity Testing Call Flow (CCR/COT)
Nicole Tan (Talk | contribs) (Adjusted the format of the callflows) |
Nicole Tan (Talk | contribs) (Edited the context) |
||
| Line 5: | Line 5: | ||
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. | ||
| − | + | A successful COT Test Callflow is as below: | |
For ITU: | For ITU: | ||
<pre> | <pre> | ||
| Line 29: | Line 29: | ||
== Incoming Continuity testing within a call == | == 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. | 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. | ||
| − | + | A successful COT Test Callflow is as below: | |
<pre> | <pre> | ||
Peer SP TMG | Peer SP TMG | ||
| Line 45: | Line 45: | ||
== Outgoing COT testing == | == Outgoing COT testing == | ||
| + | Users of the TMG unit can generate out of call SS7 ISUP Continuity Tests via webportal easily. | ||
| + | A successful COT Test Callflow is as below: | ||
<pre> | <pre> | ||
Peer SP TMG | Peer SP TMG | ||
| Line 53: | Line 55: | ||
RLC -- - - - - - - - - - -> | RLC -- - - - - - - - - - -> | ||
</pre> | </pre> | ||
| + | |||
== Configuration == | == Configuration == | ||
*[[Outgoing COT testing|Web Portal v2.7: Outgoing COT testing]] | *[[Outgoing COT testing|Web Portal v2.7: Outgoing COT testing]] | ||
Revision as of 14:12, 24 April 2014
Continuity tests are used to make sure that the SS7 ISUP interface circuit groups (CIC) are aligned with the physical links (E1/T1) properly. 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. A successful COT Test Callflow is as below: For ITU:
Peer SP TMG
IAM - - - - - - - - - - ->
Check tone - - - - - - - - - - -|
- - - - - - - - - -
REL - - - - - - - - - - ->
< -- - - - - - - - - - RLC
For ANSI:
Peer SP TMG
CCR - - - - - - - - - - ->
< -- - - - - - - - - - LPA
Check 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. A successful COT Test Callflow is as below:
Peer SP TMG
IAM - - - - - - - - - - ->
Check tone - - - - - - - - - - -|
- - - - - - - - - - -
COT (successful) - - - - - - - - -->
<- - - - - - - - - - - ACM
- - - - - - - - - - - Ringing tone
<- - - - - - - - - - - ANM
Connectivity - - - - - - - - - - Connectivity
REL - - - - - - - - - - ->
<- - - - - - - - - - - RLC
Outgoing COT testing
Users of the TMG unit can generate out of call SS7 ISUP Continuity Tests via webportal easily. A successful COT Test Callflow is as below:
Peer SP TMG
< - - - - - - - - - - - CCR
|- - - - - - - - - - - Check tone
- - - - - - - - - -
< - - - - - - - - - - - REL
RLC -- - - - - - - - - - ->
