| V5UA_TS: Valid8.com/ACATS V5UA Conformance Test Suite V.1.2, for use with SIGTRAN V5UA Signaling Tester |
|---|
| TEST SUITE OVERVIEW |
| References | |
|---|---|
| Archive/Project | voip/V5UA_ts |
| Version | 19171599 |
| Date | 09 Aug 2008 |
| Number of Scenarios | 54 |
| Number of Groups | 7 |
| Average per Group | 7 |
| GROUP/SCENARIO | TEST PURPOSE |
|---|
| V5UA_SG_Start_001 | Activate SCTP as pre-condition for other tests for SUT = SGP |
| SUT: SGP | |
| V5UA_MGC_Start | Activate SCTP as pre-condition for other tests for SUT = ASP/MGC |
| SUT: ASP | |
| V5UA_Shutdown | Deactivate SCTP |
| SUT: SGP | |
| MGC | |
|---|---|
| V5UA_MGC_5_1_1 | To check that if LMG sends primitive to send ASP Management messages to the SG. ASP sends |
| the ASP Status primitives messages sequence that transitions the ASP
to the Active state. After this sequence a new sequence taking the ASP to the Down State will be sent. SUT: SGP | |
| V5UA_MGC_5_1_2 | To check that if the ASPUP msg is acknowledged with a ACK (ASP-Down), ASP Remains in Down State |
| SUT: SGP | |
| V5UA_MGC_5_1_3 | To check that Notify (AS-Pending) will be sent if Active ASP transitions to Inactive |
| ASPs are down. SUT: SGP | |
| V5UA_MGC_5_1_4 | To check that if the local SCTP sends this indication due to the loss off connectivity to the loss |
| of connectivity to the ASPs peer, ASP will be moved to Down State.
SCTP CDI is understood as either a SHUTDOWN COMPLETE notification and COMMUNICATION LOST notification from the SCTP. SUT: SGP | |
| V5UA_MGC_5_2_1 | To check that if any message with Invalid Version is received at the ASP then ASP responds with |
| ERROR message containing cause "Invalid Version" and diagnostic
information filled with the version that the SG supports. could be down with ASP being Up). SUT: SGP | |
| V5UA_MGC_5_2_2 | To check that if a message with an undefined message type is received at AS, AS responds with ERROR |
| message containing cause "Unsupported Message Type". To chekc that if
an error message is received then this error is reported to the User. Further action at the MGC are implementation dependent. ASP is Active (The same Test Case could be down with ASP being Up.) SUT: SGP | |
| V5UA_MGC_5_2_3 | To check that if a message with message class not defined is received at AS, AS responds with |
| ERROR message containing cause "Unsupported Message Class". To check
that if an error is received then this error is reported to the User. Further action at the MGC are implementation dependent. ASP is Active (The same Test Case could be done with ASP being Up. SUT: SGP | |
| V5UA_MGC_5_2_4 | To check that if a QPTM message from an SG is received while ASP was in the Inactive state, the |
| "Unexpected Message" error would be sent by the ASP. (the ASP could
optionally drop the message and not send an Error) Pre-condition: SCTP association is established between SG and ASP. ASP is inactive. Reference: RFC3057 Clause 3.3.3.1 Status: SUT: SGP | |
| V5UA_MGC_5_3_1 | To check that if an ASP has been configured to hand traffic for more than one AS. The V5UA layer |
| at the SG maintains the availability state of all dynamically
registered remote ASPs, in SG and ASPs. As well, the active/inactive state of remote ASP(s) are also maintained. Active ASPs are those currently receiving traffic from the SG. Pre-condition: An SCTP association is established between each SG and ASP. ASP has been configured to handle traffic from two SG. ASP is Down for AS1 and AS2 Reference: RFC3057 Clause 1.3.3 Status: SUT: SGP | |
| V5UA_MGC_5_4_1 | To check that a Data Link on a Signaling Channel is established and Traffic User PDUs can be |
| exchanged. Pre-condition: SCTP association is established between SG and ASP. ASP is in ASP-Active state. Reference: RFC3057 Clause 4.1.2 Status: SUT: SGP | |
| SG | |
| V5UA_SG_6_1_1 | To check that if LMG sends primitive to send ASP Management messages to the SG. ASP sends |
| the ASP Status primitives messages sequence that transitions the ASP
to the Active state. After this sequence a new sequence taking the ASP to the Down State will be sent. ASP is down. SUT: SGP | |
| V5UA_SG_6_1_2 | To check that ASP Active is rejected if ASP not in UP state |
| ASP is down. SUT: SGP | |
| V5UA_SG_6_1_3 | To check that Notify (AS-Pending) will be sent if Active ASP transitions to Inactive |
| ASPs are down. SUT: SGP | |
| V5UA_SG_6_1_4 | To check that SG will send Notify (Alternative ASP Active) if one ASP overides another ASP |
Pre-condition: SCTP associations are established between SG and both ASPs. ASPs are down. Reference: RFC3057 Clause 4.3.2 Status: SUT: SGP | |
| V5UA_SG_6_1_5 | SCTP Communication Down Indication |
| To check that if the local SCTP sends this indication due to the loss
of connectivity to the ASPs peer, ASP will be moved to the Down State. SCTP CDI is understood as either SHUTDOWN COMPLETE notificaiton and COMMUNICATION LOST notification from the SCTP. Pre-condition: SCTP association is aestablished between SG and ASP. ASP is UP. Status: SUT: SGP | |
| V5UA_SG_6_2_1 | To check that if any message with Invalid Version is sent from SG if it receives a message that contains |
| a version it does not support. SUT: SGP | |
| V5UA_SG_6_2_2_a | To check that if a message with an undefined message type is received at SG,` |
| SG responds with ERROR message containing cause "Unsupported Message
Type". ASP is Active SUT: SGP | |
| V5UA_SG_6_2_2_b | To check that if a message with an undefined message type is received at SG,` |
| SG responds with ERROR message containing cause "Unsupported Message
Type". ASP is UP SUT: SGP | |
| V5UA_SG_6_2_3_a | To check that if a message with message class not defined is received at SG, SG responds |
| with ERROR message containing cause "Unsupported Message
Class". ASP is Active Reference: RFC3057 Clause 4.3.2 Status: SUT: SGP | |
| V5UA_SG_6_2_3_b | To check that if a message with message class not defined is received at SG, SG responds |
| with ERROR message containing cause "Unsupported Message
Class". ASP is UP Reference: RFC3057 Clause 4.3.2 Status: SUT: SGP | |
| V5UA_SG_6_2_4 | To check that the SG will respond with Error (Invalid Interface Identifer) if the ASP sends |
| a message for an Invalid Interface Identifer (one that is not
configured on SG). ASP is Active (The same Test Case could be done with ASP being up). SUT: SGP | |
| V5UA_SG_6_2_5 | To check that if a QPTM message is sent from ASP while ASP is not Active, the SG will send |
| "Unexpected Message" error in response. SUT: SGP | |
| V5UA_SG_6_3_1 | To check that if an SG can support more than one ASP. In this case, one ASP will support |
| a number of Interface Identifiers and th other ASP will support other
Interface Identifiers. Note: The Interface Identifiers must not overlap between ASPs. Both ASPs are Down. SUT: SGP | |
| V5PTM | |
| V5UA_6_4_1 | To check that a Data Link on a Signaling Channel is established and Traffic User PDUs can be |
| exchanged. Pre-condition: SCTP association is established between SG and ASP. ASP is in ASP-Active state. SUT: SGP | |
| V5UA_6_4_2 | To check that an SG will send Release Ind when Data link fails |
| SUT: SGP | |
| V5UA_6_4_3 | To check that Data can be transferred as Data PDU from MGC to SG |
| SUT: SGP | |
| V5UA_6_4_4 | To check that Data can be transferred as Data PDU from SG to MGC |
| SUT: SGP | |
| V5UA_6_4_5 | To check that Data can be transferred as Unit Data PDU from MGC to SG |
| SUT: SGP | |
| V5UA_6_4_6 | To check that Data can be transferred as Unit Data PDU from SG to MGC |
| SUT: SGP | |
| V5UA_6_4_7 | To check that when MGC sends Establish Request, SG responds with |
| Establish Confirm or Indication. SUT: SGP | |
| V5UA_6_4_8 | To check that when SG sends Establish Confirm, it does not contain any additional |
| parameters, and MGC accepts the message. SUT: SGP | |
| V5UA_6_4_9 | To check that when SG sends Establish Indication, it does not contain any additional |
| parameters, and MGC accepts the message. SUT: SGP | |
| V5UA_6_4_10 | To check that when MGC sends Release Request, SG responds with Release Confirm or Indication |
| SUT: SGP | |
| V5UA_6_4_11 | To check that when SG sends Release Confirm, it contains Reason field, and |
| MGC accepts the message. SUT: SGP | |
| V5UA_6_4_12 | To check that when SG sends Release Indication, it contains Reason field, and |
| MGC accepts the message. SUT: SGP | |
| V5UA_6_4_13 | To check that when MGC sends Link Status Start Reporting, SG responds with |
| Link Status Indication. SUT: SGP | |
| V5UA_6_4_14 | To check that when MGC sends Link Status Stop Reporting, SG sends no response |
| SUT: SGP | |
| V5UA_6_4_15 | To check that when SG sends Link Status Indication it includes Link Status field |
| with Operational or Non-Operational depending on link state. SUT: SGP | |
| V5UA_6_4_16 | To check that when MGC sends Sa-Bit Set Request, SG responds with Sa-Bit Set Confirm |
| SUT: SGP | |
| V5UA_6_4_17 | To check that when SG sends Sa-Bit Conform it includes Bit ID and Bit |
| Value fields with Zero or One, and Addresses respectively. SUT: SGP | |
| V5UA_6_4_18 | To check that when MGC sends Sa-Bit Status Request, SG responds with |
| Sa-Bit Status Indication. SUT: SGP | |
| V5UA_6_4_19 | To check that when SG sends Sa-Bit Status Indication includes Bit ID |
| and Bit Value fields with Zero or One, and Addresses
respectively. SUT: SGP | |
| V5UA_6_4_20_1 | Send Error Indication from SG to MGC with Reason value 1 = Overload |
| SUT: SGP | |
| V5UA_6_4_20_2 | Send Error Indication from SG to MGC with invalid Reason value !1 = 1 |
| and verify correct error response. SUT: SGP | |
| Tools | |
| V5UA_SG_UP_001 | Tester sends AS-UP to SG |
| Tester sends AS-UP to SG | |
| V5UA_SG_DOWN_001 | Tester sends AS-DOWN to SG |
| Tester sends AS-DOWN to SG | |
| V5UA_SG_ACTIVE_001 | Tester sends AS-ACTIVE to SG |
| Tester sends AS-ACTIVE to SG | |
| V5UA_SG_INACTIVE_001 | Tester sends AS-INACTIVE to SG |
| Tester sends AS-INACTIVE to SG | |
| Misc | |
| V5UA_Misc_SGP_ASPM_V_001 | Ensure that the IUT, upon receipt of an ASP Up message, responds with an ASP Up Ack |
| Pre-condition: Successfully established SCTP connection between SGP
and ASP Reference: Status: SUT: SGP | |
| V5UA_Misc_SGP_ASPM_V_002 | Ensure that the IUT, upon receipt of an ASP Up message, responds with an ASP Up Ack |
| Pre-condition: Successfully established SCTP connection between SGP
and ASP Reference: Status: SUT: SGP | |
| Misc2 | |
| V5UA_ALL_MSGS_MISC | |
| Test for all different message encoding variations SUT: | |
| Variable | Default Value | Description |
|---|---|---|
| N_Adaptors | 1 | (null) |
| N_Sockets | 1 | (null) |
| Adaptor_ID_1 | 1 | Adaptor ID used for testing |
| Adaptor_ID_2 | 2 | Adaptor ID used for testing |
| PCO1_Use_Primary_Address | TRUE | Use primary or secondary NIC card for this PCO |
| PCO2_Use_Primary_Address | TRUE | Use primary or secondary NIC card for this PCO |
| PCO3_Use_Primary_Address | TRUE | Use primary or secondary NIC card for this PCO |
| PCO4_Use_Primary_Address | TRUE | Use primary or secondary NIC card for this PCO |
| PCO1_Src_IP_Addr | "192.168.1.47" | (null) |
| PCO1_Src_IPv6_Addr | '00010000000000000000000000000... | (null) |
| PCO1_Dst_IP_Addr | "192.168.1.58" | (null) |
| PCO1_Dst_IPv6_Addr | '00020000000000000000000000000... | (null) |
| PCO1_Src_Port | 9900 | (null) |
| PCO1_Dst_Port | 9900 | (null) |
| PCO1_2_Src_IP_Addr | "192.168.5.47" | (null) |
| PCO1_2_Dst_IP_Addr | "192.168.5.58" | (null) |
| PCO1_2_Src_Port | 9900 | (null) |
| PCO1_2_Dst_Port | 9900 | (null) |
| PCO2_Src_IP_Addr | "192.168.2.51" | (null) |
| PCO2_Dst_IP_Addr | "192.168.2.52" | (null) |
| PCO2_Src_Port | 50001 | (null) |
| PCO2_Dst_Port | 50001 | (null) |
| PCO2_2_Src_IP_Addr | "192.168.5.47" | (null) |
| PCO2_2_Dst_IP_Addr | "192.168.5.58" | (null) |
| PCO2_2_Src_Port | 9900 | (null) |
| PCO2_2_Dst_Port | 9900 | (null) |
| PCO3_Src_IP_Addr | "192.168.3.51" | (null) |
| PCO3_Dst_IP_Addr | "192.168.3.52" | (null) |
| PCO3_Src_Port | 50001 | (null) |
| PCO3_Dst_Port | 50001 | (null) |
| PCO3_2_Src_IP_Addr | "192.168.5.47" | (null) |
| PCO3_2_Dst_IP_Addr | "192.168.5.58" | (null) |
| PCO3_2_Src_Port | 9900 | (null) |
| PCO3_2_Dst_Port | 9900 | (null) |
| PCO4_Src_IP_Addr | "192.168.4.51" | (null) |
| PCO4_Dst_IP_Addr | "192.168.4.52" | (null) |
| PCO4_Src_Port | 50001 | (null) |
| PCO4_Dst_Port | 50001 | (null) |
| PCO4_2_Src_IP_Addr | "192.168.5.47" | (null) |
| PCO4_2_Dst_IP_Addr | "192.168.5.58" | (null) |
| PCO4_2_Src_Port | 9900 | (null) |
| PCO4_2_Dst_Port | 9900 | (null) |
| PCO1_Adaptor_ID | 1 | Adaptor ID used for testing |
| PCO2_Adaptor_ID | 2 | Adaptor ID used for testing |
| Layer_3_Protocol | Use_IPv4 | Network layer; above Ethernet, default = Use_IPv4 |
| Status_Type | 1 | (null) |
| In_Status_Type | 1 | (null) |
| Status_ID | 1 | (null) |
| In_Status_ID | 1 | (null) |
| Provisioned | (null) | (null) |
| Process_Type | (null) | (null) |
| AutoStart_After_Time | 1000 | (null) |
| Mgmt_StreamID | 0 | (null) |
| Data_StreamID | 2 | (null) |
| Interface_ID | 100 | (null) |
| Interface_ID_2 | 100 | (null) |
| Interface_ID_Invalid | 999 | (null) |
| DLCI | 1 | (null) |
| SAPI | 1 | (null) |
| TEI | 1 | (null) |
| Channel_Num | 1 | (null) |
| All_Channels | (null) | (null) |
| N_Output_Streams | 2 | Number of Tester SCTP Output streams |
| N_Input_Streams | 2 | Number of Tester SCTP Input streams |
| Encoding_Type | (null) | (null) |
| EMS_Traffic_Mode_1210 | (null) | (null) |
| Traffic_Mode | Over_Ride | (null) |
| Reason | Management_Inhibit | (null) |
| ASP_ID_1 | 1 | (null) |
| ASP_ID_2 | 2 | (null) |
| Bit_ID | 0 | (null) |
| Bit_Value | 7 | (null) |
| Copyright © ACATS Forum 2008 on behalf of the test suite author. All rights reserved. Specifications may change subject to requirements. |
| 09 Aug 2008 | Produced by SAFIRE V20.05.14.01 www.SAFIRE-World.com |
Test Suite Overview |