M3UA_TS: Valid8.com/ACATS M3UA Conformance Test Suite V.2.7, for use with SIGTRAN M3UA Signaling Tester
TEST SUITE OVERVIEW
References
Archive/Project voip/m3ua_ts
Version 19171599
Date 09 Aug 2008
Number of Scenarios 145
Number of Groups 28
Average per Group 5
GROUP/SCENARIO TEST PURPOSE
M3UA_SG_Start Activate SCTP as pre-condition for other tests for SUT = SGP
SUT: SGP
M3UA_ASP_Start Activate SCTP as pre-condition for other tests for SUT = ASP/MGC
SUT: ASP/MGC/MGC
M3UA_Shutdown Deactivate SCTP
SUT: SGP
M3UA_SGP
M3UA_SGP/
M3UA_SGP_ASPSM
M3UA_SGP/
M3UA_SGP_ASPSM/
M3UA_SGP_ASPSM_V
M3UA_SGP_ASPSM_V_001 Ensure that the IUT, upon receipt of an ASP Up message, responds with an ASP Up Ack
SUT: SGP
M3UA_SGP_ASPSM_V_003 Ensure that the IUT, upon reception of an ASP Up message, responds with an ASP Up Ack
and sends a NOTIFY message indicating the AS state change to AS-INACTIVE
One ASP configured within the AS.
ASP marked as ASP-DOWN at the SGP.
SUT: SGP
M3UA_SGP_ASPSM_V_005 Ensure that the IUT, upon reception of an ASP Down message, responds with an ASP Down Ack
SP marked as ASP-INACTIVE at the ASP
SUT: SGP
M3UA_SGP_ASPSM_V_009 Ensure that the IUT, upon reception of an ASP Up message sent by an ASP marked as blocked at the
SGP, responds with an ERROR message with reason 0x0d "Refused - Management Blocking"
ASP marked as blocked at the SGP
Reference: RFC4666, ETSI TS 102 381 V1.1.1 (2004-12) Section 3.8.1 [1], Section 4.3.4.1 [1]
SUT: SGP
M3UA_SGP/
M3UA_SGP_ASPSM/
M3UA_SGP_ASPSM_I
M3UA_SGP_ASPSM_I_001 Ensure that the IUT, upon reception of an ASP Up message that contains an invalid M3UA
version (e.g. 2), responds with an ERROR message with reason 0x01 ("Invalid Version")
Reference: RFC4666, ETSI TS 102 381 V1.1.1 (2004-12) Section 3.1.1 [1],Section 3.8.1 [1], Section 4.3.4.1.1 [1]
SUT: SGP
M3UA_SGP_ASPSM_I_002 Ensure that the IUT, upon reception of a message which class is 3 (ASPSM)
and type is different from 0 (Reserved) 1(ASP Up), 2 (ASP Down), 3 (BEAT), 4
(ASP Up Ack), 5 (ASP Down Ack) and 6 (BEAT Ack) responds with an ERROR message
with reason 0x04 "Unsupported Message Type"
ASP marked as ASP-DOWN at the SGP
SUT: SGP
M3UA_SGP_ASPSM_I_003 Ensure that the IUT, upon reception of a message which class is 4 (ASPTM) responds with an
ERROR message with reason 0x06 "Unsupported Message" or silently discard the message.
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-DOWN at the SGP
One ASP in the AS
SUT: SGP
M3UA_SGP_ASPSM_I_004 Ensure that the IUT, upon reception of a message which class is 3 (ASPSM) and type is different
from 0 (Reserved) 1(ASP Up), 2 (ASP Down), 3 (BEAT), 4 (ASP Up Ack), 5 (ASP Down Ack) and 6 (BEAT Ack)
responds with an ERROR message with reason 0x04 "Unsupported Message Type"
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-INACTIVE at the SGP
SUT: SGP
M3UA_SGP/
M3UA_SGP_ASPSM/
M3UA_SGP_ASPSM_O
M3UA_SGP_ASPSM_O_001 Ensure that the IUT, upon reception of an ASP Up message, responds with an ASP Up Ack
ASP marked as ASP-INACTIVE at the SGP
SUT: SGP
M3UA_SGP_ASPSM_O_001_DEMO Ensure that the IUT, upon reception of an ASP Up message, responds with an ASP Up Ack
ASP marked as ASP-INACTIVE at the SGP
SUT: SGP
M3UA_SGP_ASPSM_O_003 Ensure that the IUT, upon reception of an ASP Up message, responds with an ASP Up Ack,
sends an ERROR message with reason 0x06 "Unexpected Message" and sends a NOTIFY message
indicating the AS state change to AS-INACTIVE
ASP marked as ASP-ACTIVE at the SGP
One ASP in the AS
SUT: SGP
M3UA_SGP_ASPSM_O_004 Ensure that the IUT, upon reception of an ASP Down message, responds with an ASP Down Ack
ASP marked as ASP-DOWN at the SGP
SUT: SGP
M3UA_SGP/
M3UA_SGP_ASPTM
M3UA_SGP/
M3UA_SGP_ASPTM/
M3UA_SGP_ASPTM_V
M3UA_SGP_ASPTM_V_001 Ensure that the IUT, upon reception of an ASP Active message, responds with an ASP Active Ack
ASP marked as ASP-INACTIVE at the SGP
SUT: SGP
M3UA_SGP_ASPTM_V_003 Ensure that the IUT, upon reception of an ASP Active message, responds with an ASP Active Ack
and sends a NOTIFY message indicating the AS state change to AS-ACTIVE
One ASP Configured in the AS
ASP marked as ASP-INACTIVE at the SGP
SUT: SGP
M3UA_SGP_ASPTM_V_005 Ensure that the IUT, upon reception of an ASP Active message that contains a Routing Context,
responds with an ASP Active Ack that contains the Routing Context
ASP marked as ASP-INACTIVE at the SGP
SUT: SGP
M3UA_SGP_ASPTM_V_006 Ensure that the IUT, upon reception of an ASP Inactive message, responds with an ASP Inactive Ack
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-ACTIVE at the SGP
SUT: SGP
M3UA_SGP_ASPTM_V_008 Ensure that the IUT, upon reception of an ASP Inactive message, responds with an ASP Inactive Ack
and sends a NOTIFY message indicating the AS state change to AS-PENDING
ASP marked as ASP-ACTIVE at the SGP
One ASP in the AS
SUT: SGP
M3UA_SGP_ASPTM_V_010 Ensure that the IUT, upon reception of a Heartbeat message, responds with a Heartbeat Ack
ASP marked as ASP-ACTIVE at the SGP
Status: Mandatory
SUT: SGP
M3UA_SGP_ASPTM_V_011 Ensure that the IUT, upon reception of a Heartbeat message that contains an opaque
Heartbeat Data parameter, responds with a Heartbeat Ack that echoes back unchanged the
opaque Heartbeat Data parameter
ASP marked as ASP-ACTIVE at the SGP
Status: Mandatory
SUT: SGP
M3UA_SGP_ASPTM_V_013 Ensure that the IUT, upon reception of an ASP Inactive message from ASP1 responds with an ASP
Inactive Ack and sends a NOTIFY message with status "Insufficient ASP Resources Active in AS"
to all Inactive ASPs
2 ASP in the AS
Both ASPs marked as ASP ACTIVE at the SGP
AS configure in Broadcast mode
** Multiple ASPs Not Supported **
SUT: SGP
M3UA_SGP_ASPTM_V_014 Ensure that the IUT, upon reception of an ASP Active message from ASP1 that indicates a Traffic
Handling Type of "Override", responds with an ASP Active Ack and sends a NOTIFY message with status
"Alternate ASP Active" to ASP 2
2 ASP in the AS
ASP1 marked as ASP INACTIVE at the SGP
ASP2 marked as ASP ACTIVE at the SGP
ASP1 and ASP2 configured in "Override" mode
SUT: SGP
M3UA_SGP_ASPTM_V_015 Ensure that the IUT, upon reception of an ASP Active message from ASP1 that indicates a Traffic
Handling Type of "Override", responds with an ASP Active Ack and sends a NOTIFY message with status
"Alternate ASP Active" to ASP 2 that includes the ASP ID of the Alternate ASP
Pre-condition: Successfully established SCTP association between the SGP and the ASP
2 ASP in the AS
ASP1 marked as ASP INACTIVE at the SGP
ASP2 marked as ASP ACTIVE at the SGP
Reference: RFC4666, ETSI TS 102 381 V1.1.1 (2004-12) Section 3.8.2 [1], Section 4.3.4.3 [1]
SUT: SGP
M3UA_SGP/
M3UA_SGP_ASPTM/
M3UA_SGP_ASPTM_I
M3UA_SGP_ASPTM_I_001 Ensure that the IUT, upon reception of an ASP Active message that contains an invalid M3UA
version (e.g. 2), responds with an ERROR message with reason 0x01 ("Invalid Version")
ASP marked as ASP-INACTIVE at the SGP
Reference: RFC4666, ETSI TS 102 381 V1.1.1 (2004-12) Section 3.1.1 [1], Section 3.8.1 [1], Section 4.3.1 [1], Section 4.3.4.3 [1]
Status: Optional
SUT: SGP
M3UA_SGP_ASPTM_I_003 Ensure that the IUT, upon reception of an ASP Active, that indicates a Traffic Mode Type of
"Broadcast", responds with an ERROR message with reason 0x05 "Unsupported Traffic Mode Type"
ASP marked as ASP-INACTIVE at the SGP
One ASP in the AS
SUT: SGP
M3UA_SGP_ASPTM_I_004 Ensure that the IUT, upon reception of an ASP Active, that indicates a Traffic Mode Type of "4"
(i.e. not valid), responds with an ERROR message with reason 0x05 "Unsupported Traffic Mode Type"
ASP marked as ASP-INACTIVE at the SGP
One ASP in the AS
SUT: SGP
M3UA_SGP_ASPTM_I_005 Ensure that the IUT, upon reception of an ASP Active message that contains a Routing Context
which cannot be activated has not been provisioned at the SGP, responds with ERROR message with reason "Invalid Routing Context"
ASP marked as ASP-INACTIVE at the SGP
SUT: SGP
M3UA_SGP_ASPTM_I_006 Ensure that the IUT, upon reception of a message which class is 4 (ASPTM) and type is
different from 0 (Reserved) 1(ASP Active), 2 (ASP Inactive), 3 (ASP Active Ack), and 4
(ASP Inactive Ack) responds with an ERROR message with reason 0x04 "Unsupported Message Type"
ASP marked as ASP-INACTIVE at the SGP
SUT: SGP
M3UA_SGP_ASPTM_I_008 Ensure that the IUT, upon reception of a message which class is 4 (ASPTM) and type is different
from 0 (Reserved) 1(ASP Active), 2 (ASP Inactive), 3 (ASP Active Ack), and 4 (ASP Inactive Ack)
responds with an ERROR message with reason 0x04 "Unsupported Message Type"
ASP marked as ASP-ACTIVE at the SGP
SUT: SGP
M3UA_SGP_ASPTM_I_009 Ensure that the IUT that has lost SCTP connectivity with ASP1 sends a NOTIFY
message with status "ASP Failure" to ASP2
2 ASPs in AS
ASPs marked as ASP-ACTIVE at the SGP
Status: Optional
SUT: SGP
M3UA_SGP_ASPTM_I_010 Ensure that the IUT upon reception of an ASP Inactive message, responds
with an ASP Inactive Ack which Message Length, in the Common Message Header, includes the parameter padding bytes, if any.
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-ACTIVE at the SGP
Status: Mandatory
SUT: SGP
M3UA_SGP/
M3UA_SGP_ASPTM/
M3UA_SGP_ASPTM_O
M3UA_SGP_ASPTM_O_001 Ensure that the IUT, upon reception of an ASP Active, responds with an ASP Active Ack
ASP marked as ASP-ACTIVE at the SGP
SUT: SGP
M3UA_SGP_ASPTM_O_003 Ensure that the IUT, upon reception of an ASP Inactive, responds with an ASP Inactive Ack
ASP marked as ASP-INACTIVE at the SGP
SUT: SGP
M3UA_SGP/
M3UA_SGP_MTR
M3UA_SGP/
M3UA_SGP_MTR/
M3UA_SGP_MTR_V
M3UA_SGP_MTR_V_001 Ensure that the IUT includes a valid Routing Context in any Payload Data Message
ASPs marked as ASP Active at the SGP
Multiple Routing Keys and Routing Contexts are being used across a common association
SUT: SGP
M3UA_SGP_MTR_V_002 Ensure that the IUT includes the Protocol Data parameter in any Payload Data Message
ASPs marked as ASP Active at the SGP
Multiple Routing Keys and Routing Contexts are being used across a common association
SUT: SGP
M3UA_SGP_MTR_V_003 Ensure that the IUT sends DATA messages on an any valid SCTP stream other than stream "0"
SUT: SGP
M3UA_SGP_MTR_V_004 Ensure that the IUT tags the first DATA message broadcast whenever an ASP becomes active
AS configured as Broadcast mode
At least one ASP within the
AS marked as ASP-ACTIVE
SUT: SGP
M3UA_SGP_MTR_V_005x Ensure that the IUT accepts a valid Payload Data Message
ASPs marked as ASP Active at the SGP
Multiple Routing Keys and Routing Contexts are being used across a common association
SUT: SGP
M3UA_SGP/
M3UA_SGP_MTR/
M3UA_SGP_MTR_I
M3UA_SGP_MTR_I_001 Ensure that the IUT, upon reception of a DATA message that specifies a protocol version 2,
responds with an ERROR message with reason 0x01 "Invalid Version"
ASP marked as ASP-ACTIVE at the SGP
SUT: SGP
M3UA_SGP_MTR_I_002 Ensure that the IUT, upon reception of a message that specifies a class different from 0
("Management Message"), 1 ("Transfer Message"), 2 ("SS7 Signalling Network Message"), 3
("ASP State Maintenance Message"), 4 ("ASP Traffic Maintenance Message"), or 9
("Routing Key Management"), responds with an ERROR message with reason 0x03
"Unsupported Message Class"
ASP marked as ASP-ACTIVE at the SGP
SUT: SGP
M3UA_SGP_MTR_I_003 Ensure that the IUT, upon reception of a message that specifies a class equal to 1
("Transfer Message") and a type different from 0 ("Reserved"), and 1 ("Payload DATA")
responds with an ERROR message with reason 0x04 "Unsupported Message Type"
ASP marked as ASP-ACTIVE at the SGP
SUT: SGP
M3UA_SGP/
M3UA_SGP_RKM
M3UA_SGP/
M3UA_SGP_RKM/
M3UA_SGP_RKM_V
M3UA_SGP_RKM_V_001 Ensure that the IUT, upon reception of a REG REQ that contains a Routing Key which matches
an existing SGP Routing Key and which ASP is not currently included in the list of ASPs for
the related AS, responds with REG RSP with Registration Result 0 "Successfully Registered"
ASP marked as ASP-INACTIVE at the SGP
SGP does support the registration Routing Key Management Procedures
SUT: SGP
M3UA_SGP_RKM_V_002 Ensure that the IUT, upon reception of a REG REQ that contains a Routing Key which does not
currently exist, responds with REG RSP with Registration Result 0 "Successfully Registered"
ASP marked as ASP-INACTIVE at the SGP
SGP does support the Routing Key Management Procedures
SGP does support dynamic configuration of Routing Key
SUT: SGP
M3UA_SGP_RKM_V_003 Ensure that the IUT, upon reception of a DEREG REQ, responds with DEREG RSP with
Deregistration Result 0 "Successfully Deregistered"
ASP marked as ASP-INACTIVE at the SGP
SGP does support the Routing Key Management Procedures registration procedure
SGP does support dynamic configuration of Routing Keys
ASP registered at the SGP
** RKM not verified in this release **
SUT: SGP
M3UA_SGP_RKM_V_004 Ensure that the IUT, upon reception of a REG REQ responds with an ERROR message with
reason 0x03 "Unsupported Message Class"
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-INACTIVE at the SGP
SGP does not support the Routing Key Management Procedures
SUT: SGP
M3UA_SGP/
M3UA_SGP_RKM/
M3UA_SGP_RKM_I
M3UA_SGP_RKM_I_003 Ensure that the IUT, upon reception of a REG REQ that contains an invalid Routing Key,
responds with a REG RSP message with Registration Result 4 "Error - Invalid Routing Key"
ASP marked as ASP-INACTIVE at the SGP
SGP does support the Routing Key Management Procedures
** RKM not verified in this release **
SUT: SGP
M3UA_SGP_RKM_I_004 Ensure that the IUT, upon reception of a REG REQ that contains an invalid Destination
Point Code (DPC), responds with a REG RSP message with Registration Result 2
"Error - Invalid DPC"
ASP marked as ASP-INACTIVE at the SGP
SGP does support the Routing Key Management Procedures
SUT: SGP
M3UA_SGP_RKM_I_005 Ensure that the IUT, upon reception of a REG REQ that contains an invalid Network Appearance,
responds with a REG RSP message with Registration Result 2 "Error - Invalid Network Appearance"
ASP marked as ASP-INACTIVE at the SGP
SGP does support the Routing Key Management Procedures
SUT: SGP
M3UA_SGP_RKM_I_006 Ensure that the IUT, upon reception of a REG REQ with a Routing Key that is completely identical
to an existing Routing Key, responds with a REG RSP message with Registration Result 6
"Error - Cannot Support Unique Routing" if it determines that a unique Routing Key cannot be created
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-INACTIVE at the SGP
SGP does support the Routing Key Management Procedures
** RKM not verified in this release **
SUT: SGP
M3UA_SGP_RKM_I_007 Ensure that the IUT, upon reception of a REG REQ that cannot be authorized,
responds with a REG RSP with Registration Result 5 "Error - Permission Denied"
ASP marked as ASP-INACTIVE at the SGP
SGP does support the Routing Key Management Procedures
SUT: SGP
M3UA_SGP_RKM_I_008 Ensure that the IUT, upon reception of a REG REQ that contains a Routing Key that does not exist,
responds with a REG RSP with Registration Result 7 "Error - Routing Key not Currently Provisioned"
ASP marked as ASP-INACTIVE at the SGP
SGP does support the Routing Key Management Procedures
SGP does not support dynamic configuration
** RKM not verified in this release **
SUT: SGP
M3UA_SGP_RKM_I_009 Ensure that the IUT, upon reception of a REG REQ that contains a Routing Key which does not currently
exist, responds with a REG RSP with Registration Result 8 "Error - Insufficient Resources" if it does
not have the capacity to add a new Routing Key and AS entries
ASP marked as ASP-INACTIVE at the SGP
SGP does support the Routing Key Management Procedures
SGP does support dynamic configuration of Routing Keys
SUT: SGP
M3UA_SGP_RKM_I_010 Ensure that the IUT, upon reception of a REG REQ that contains parameters used for creating
the new Routing Key entries that are not supported, responds with a REG RSP with Registration
Result 9 "Error - Unsupported RK Parameter Field"
ASP marked as ASP-INACTIVE at the SGP
SGP does support the Routing Key Management Procedures
SGP does support dynamic configuration of Routing Keys
SUT: SGP
M3UA_SGP_RKM_I_011 Ensure that the IUT, upon reception of a a first REG REQ that specifies a Traffic Mode Type
of Override, followed, once the first REG REQ has been ACKed, by a second REG REQ that specifies
a Traffic Mode Type of Loadshare, responds to the second REG REQ with a REG RSP with Registration
Result 10 "Error - Unsupported/Invalid Traffic Handling Mode"
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-INACTIVE at the SGP
AS in Override mode
SGP does support the Routing Key Management Procedures
SGP does support dynamic configuration of Routing Keys
SUT: SGP
M3UA_SGP_RKM_I_012 Ensure that the IUT, upon reception of aa first REG REQ that specifies a Traffic Mode Type
of Override, followed, once the first REG REQ has been ACKed, by a second REG REQ that specifies
a Traffic Mode Type of Broadcast, responds to the second REG REQ with a REG RSP with Registration
Result 10 "Error - Unsupported/Invalid Traffic Handling Mode"
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-INACTIVE at the SGP
AS in Override mode
SGP does support the Routing Key Management Procedures
SGP does support dynamic configuration of Routing Keys
** RKM not verified in this release **
SUT: SGP
M3UA_SGP_RKM_I_013 Ensure that the IUT, upon reception of a REG REQ that specifies a Traffic Mode Type
of 4 (i.e. invalid), responds with a REG RSP with Registration Result 10 "Error -
Unsupported/Invalid Traffic Handling Mode"
ASP marked as ASP-INACTIVE at the SGP
SGP does support the Routing Key Management Procedures
SGP does support dynamic configuration of Routing Keys
** RKM not verified in this release **
SUT: SGP
M3UA_SGP_RKM_I_014 Ensure that the IUT, upon reception of a first REG REQ that specifies a Traffic Mode Type of
Loadshare, followed, once the first REG REQ has been ACKed, by a second a REG REQ that specifies
a Traffic Mode Type of Override, responds to the second REG REQ with a REG RSP with Registration
Result 10 "Error - Unsupported/Invalid Traffic Handling Mode"
ASP marked as ASP-INACTIVE at the SGP
AS in Loadshare mode
SGP does support the Routing Key Management Procedures
SGP does support dynamic configuration of Routing Keys
SUT: SGP
M3UA_SGP_RKM_I_015 Ensure that the IUT, upon reception of a first REG REQ that specifies a Traffic Mode Type of
Loadshare, followed, once the first REG REQ has been ACKed, by a second REG REQ that specifies
a Traffic Mode Type of Broadcast, responds to the second REQ REQ with a REG RSP with Registration
Result 10 "Error - Unsupported/Invalid Traffic Handling Mode"
ASP marked as ASP-INACTIVE at the SGP
AS in Loadshare mode
SGP does support the Routing Key Management Procedures
SGP does support dynamic configuration of Routing Keys
SUT: SGP
M3UA_SGP_RKM_I_017 Ensure that the IUT, upon reception of a a first REG REQ that specifies a Traffic Mode Type
of Broadcast, followed, once the first REG REQ has been ACKed, by a second REG REQ that specifies
a Traffic Mode Type of Override, responds to the second REG REQ with a REG RSP with Registration
Result 10 "Error - Unsupported/Invalid Traffic Handling Mode"
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-INACTIVE at the SGP
AS in Broadcast mode
SGP does support the Routing Key Management Procedures
SGP does support dynamic configuration of Routing Keys
SUT: SGP
M3UA_SGP_RKM_I_018 Ensure that the IUT, upon reception of a first REG REQ that specifies a Traffic Mode
Type of Broadcast, followed, once the first REG REQ has been ACKed, by a second REG REQ
that specifies a Traffic Mode Type of Loadshare, responds to the second REG REQ with a
REG RSP with Registration Result 10 "Error - Unsupported/Invalid Traffic Handling Mode"
ASP marked as ASP-INACTIVE at the SGP
AS in Broadcast mode
SGP does support the Routing Key Management Procedures
SGP does support dynamic configuration of Routing Keys
SUT: SGP
M3UA_SGP_RKM_I_020 Ensure that the IUT, upon reception of a DEREG REQ for a Routing Context that was not registered,
responds with a DEREG RSP with Deregistration Result 4 "Error - Not Registered"
ASP marked as ASP-INACTIVE at the SGP
SGP does support the Routing Key Management Procedures
SGP does support dynamic configuration of Routing Keys
** RKM not verified in this release **
SUT: SGP
M3UA_SGP_RKM_I_021 Ensure that the IUT, upon reception of a DEREG REQ for a Routing Context that was registered but
not authorized to deregister, responds with a DEREG RSP with Deregistration Result 3
"Error - Permission Denied"
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-INACTIVE at the SGP
SGP does support the Routing Key Management Procedures
SGP does support dynamic configuration of Routing Keys registered
** RKM not verified in this release **
SUT: SGP
M3UA_SGP_RKM_I_022 Ensure that the IUT, upon reception of a DEREG REQ issued by an ASP marked as ASP Active
in that Routing Context, responds with a DEREG RSP with Deregistration Result 5
"Error - ASP Currently Active for Routing Context"
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-ACTIVE at the SGP
SGP does support the Routing Key Management Procedures
SGP does support dynamic configuration of Routing Keys
SUT: SGP
M3UA_SGP_RKM_I_023 Ensure that the IUT, upon reception of a message which class is 9 (RKM) and type is different
from 0 ("Reserved"), 1 ("Registration Request"), 2 ("Registration Response"),
3 ("Deregistration Request"), and 4 ("Deregistration Response"), responds with an ERROR
message with reason 0x04 ("Unsupported Message Type")
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-ACTIVE at the SGP
SGP does support the Routing Key Management Procedures
SGP does support dynamic configuration of Routing Keys
SUT: SGP
M3UA_ASP
M3UA_ASP/
M3UA_ASP_ASPSM
M3UA_ASP/
M3UA_ASP_ASPSM/
M3UA_ASP_ASPSM_V
M3UA_ASP_ASPSM_V_002 Ensure that the IUT sends an ASP Up with a Version in the Common Message Header set to 1
ASP marked as ASP-DOWN at the SGP
SUT: ASP/MGC/MGC
M3UA_ASP_ASPSM_V_005 Ensure that the IUT sends an ASP Down with a Version in the Common Message Header set to 1
ASP marked as ASP-INACTIVE at the SGP
SUT: ASP/MGC/MGC
M3UA_ASP/
M3UA_ASP_ASPSM/
M3UA_ASP_ASPSM_I
M3UA_ASP_ASPSM_I_001 Ensure that the IUT, upon reception of an ASP Up Ack that indicates a version 2 of the M3UA protocol,
responds with an ERROR message with reason 0x01 "Invalid Version"
ASP marked as ASP-INACTIVE at the SGP
SUT: ASP/MGC/MGC
M3UA_ASP_ASPSM_I_002 Ensure that the IUT, upon reception of an ASP Down Ack that indicates a version 2 of the
M3UA protocol, responds with an ERROR message with reason 0x01 "Invalid Version"
ASP marked as ASP-INACTIVE at the SGP
SUT: ASP/MGC/MGC
M3UA_ASP_ASPSM_I_003 Ensure that the IUT, after sending an ASP Up, upon reception of a message which class
is 3 (ASPSM) and type is different from 0 (Reserved) 1(ASP Up), 2 (ASP Down), 3 (Heartbeat),
4 (ASP Up Ack), and 5 (ASP Down Ack) responds with an ERROR message with reason 0x04
"Unsupported Message Type"
ASP marked as ASP-INACTIVE at the SGP
SUT: ASP/MGC/MGC
M3UA_ASP/
M3UA_ASP_ASPSM/
M3UA_ASP_ASPSM_O
M3UA_ASP_ASPSM_O_001 Ensure that the IUT, after sending an ASP Up, upon reception of an ASP Down Ack, does not send
an ASP Active
ASP marked as ASP-DOWN at the SGP
SUT: ASP/MGC
M3UA_ASP_ASPSM_O_002 Ensure that the IUT, after sending an ASP Up, upon reception of an ASP Active Ack, does not
send DATA messages
ASP marked as ASP-DOWN at the SGP
SUT: ASP/MGC
M3UA_ASP/
M3UA_ASP_ASPTM
M3UA_ASP/
M3UA_ASP_ASPTM/
M3UA_ASP_ASPTM_V
M3UA_ASP_ASPTM_V_001 Ensure that the IUT sends an ASP Active to indicate that it is ready to start processing traffic
ASP marked as ASP-INACTIVE at the SGP
SUT: ASP/MGC
M3UA_ASP_ASPTM_V_002 Ensure that the IUT sends an ASP Active with a Version in the Common Message Header set to 1
ASP marked as ASP-INACTIVE at the SGP
Status: Optional
SUT: ASP/MGC
M3UA_ASP_ASPTM_V_005 Ensure that the IUT sends an ASP Inactive with a Version in the Common Message Header set to 1
ASP marked as ASP-ACTIVE at the SGP
Status: Optional
SUT: ASP/MGC
M3UA_ASP_ASPTM_V_007 Ensure that the IUT, upon reception of a Heartbeat message, responds with a Heartbeat Ack
ASP marked as ASP-ACTIVE at the SGP
Status: Mandatory
SUT: ASP/MGC
M3UA_ASP_ASPTM_V_008 Ensure that the IUT, upon reception of a Heartbeat message that contains an opaque Heartbeat
Data parameter, responds with a Heartbeat Ack that echoes back unchanged the opaque Heartbeat
Data parameter
ASP marked as ASP-ACTIVE at the SGP
Reference: RFC4666, ETSI TS 102 381 V1.1.1 (2004-12) Section 4.3.4.6 [1]
Status: Mandatory
SUT: ASP/MGC
M3UA_ASP/
M3UA_ASP_ASPTM/
M3UA_ASP_ASPTM_I
M3UA_ASP_ASPTM_I_001 Ensure that the IUT, upon reception of an ASP Active Ack that indicates a version 2 of the M3UA
protocol, responds with an ERROR message with reason 0x01 "Invalid Version" and does not send DATA
messages since the ASP Active Ack was invalid.
ASP marked as ASP-INACTIVE at the SGP
SUT: ASP/MGC
M3UA_ASP_ASPTM_I_002 : Ensure that the IUT, upon reception of an ASP Inactive Ack that indicates a version 2 of the
M3UA protocol, responds with an ERROR message with reason 0x01 "Invalid Version
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-INACTIVE at the SGP
SUT: ASP/MGC
M3UA_ASP_ASPTM_I_003 Ensure that the IUT, after sending an ASP Active, upon reception of a message which class is
4 (ASPTM) and type is different from 0 (Reserved) 1(ASP Active), 2 (ASP Inactive), 3
(ASP Active Ack), and 4 (ASP Inactive Ack), responds with an ERROR message with reason 0x04
"Unsupported Message Type"
ASP marked as ASP-DOWN at the SGP
SUT: ASP/MGC
M3UA_ASP/
M3UA_ASP_ASPTM/
M3UA_ASP_ASPTM_O
M3UA_ASP_ASPTM_O_001 Ensure that the IUT, after sending an ASP Active, upon reception of an ASP Up Ack, does not send DATA messages
ASP marked as ASP-INACTIVE at the SGP
SUT: ASP/MGC
M3UA_ASP/
M3UA_ASP_MTR
M3UA_ASP/
M3UA_ASP_MTR/
M3UA_ASP_MTR_V
M3UA_ASP_MTR_V_001 Ensure that the IUT includes the Routing Context in any Payload Data Message
ASPs marked as ASP Active at the SGP
Multiple Routing Keys and Routing Contexts are being used across a common association
SUT: ASP/MGC
M3UA_ASP_MTR_V_002 Ensure that the IUT includes the Protocol Data parameter in any Payload Data Message
ASPs marked as ASP Active at the SGP
Multiple Routing Keys and Routing Contexts are being used across a common association
SUT: ASP/MGC
M3UA_ASP_MTR_V_003 Ensure that the IUT sends DATA messages on an a valid SCTP stream other than stream "0"
SUT: ASP/MGC
M3UA_ASP/
M3UA_ASP_MTR/
M3UA_ASP_MTR_I
M3UA_ASP_MTR_I_001 Ensure that the IUT, upon reception of a DATA message that specifies a protocol version 2,
responds with an ERROR message with reason 0x01 "Invalid Version"
ASP marked as ASP-ACTIVE at the SGP
Status: Optional
SUT: ASP/MGC
M3UA_ASP_MTR_I_002 Ensure that the IUT, upon reception of a message that specifies a class different from 0
("Management Message"), 1 ("Transfer Message"), 2 ("SS7 Signalling Network Message"), 3
("ASP State Maintenance Message"), 4 ("ASP Traffic Maintenance Message"), or 9
("Routing Key Management"), responds with an ERROR message with reason 0x03 "Unsupported
Message Class"
ASP marked as ASP-ACTIVE at the SGP
SUT: ASP/MGC
M3UA_ASP_MTR_I_003 Ensure that the IUT, upon reception of a message that specifies a class equal to 1 ("Transfer Message")
and a type different from 0 ("Reserved"), and 1 ("Payload DATA") responds with an ERROR message with
reason 0x04 "Unsupported Message Type"
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-ACTIVE at the SGP
Reference: RFC4666, ETSI TS 102 381 V1.1.1 (2004-12) Section 3.1.2 [1], Section 3.8.1 [1]
Status: Mandatory
SUT: ASP/MGC
M3UA_ASP/
M3UA_ASP_RKM
M3UA_ASP/
M3UA_ASP_RKM/
M3UA_ASP_RKM_V
M3UA_ASP_RKM_V_002 Ensure that the IUT sends a REG REQ that contains a valid Routing Key when it wishes to dynamically register
with an SGP as an ASP within an AS.
ASP marked as ASP-INACTIVE at the SGP
SGP does support the registration procedureRouting Key Management Procedures
SGP does support dynamic configurationSGP does support dynamic configuration of Routing Keys
Reference: RFC4666, ETSI TS 102 381 V1.1.1 (2004-12) Section 3.6.1 [1], Section 4.4.1 [1]
SUT: ASP/MGC
M3UA_ASP_RKM_V_003 Ensure that the IUT sends a DEREG REQ when it wishes to deregister with an SGP as an ASP within an AS
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-INACTIVE at the SGP
SGP does support the registration procedureRouting Key Management Procedures
SGP does support dynamic configuration
ASP Registered
Reference: RFC4666, ETSI TS 102 381 V1.1.1 (2004-12) Section 3.6.3 [1], Section 4.4.2 [1]
Status: Optional
SUT: ASP/MGC
M3UA_ASP_RKM_V_004 Ensure that the IUT sends a DEREG REQ that includes the Routing Context returned by the SGP in the REG RSP
when registration occurred when it wishes to deregister with an SGP as an ASP within an AS.
Pre-condition: Successfully established SCTP association between the SGP and the ASP
ASP marked as ASP-INACTIVE at the SGP
SGP does support the registration procedure Routing Key Management Procedures
SGP does support dynamic configurationSGP does support dynamic configuration of Routing Keys
ASP Registered
Reference: RFC4666, ETSI TS 102 381 V1.1.1 (2004-12) Section 3.6.2 [1], Section 3.6.3 [1], Section 4.4.2 [1]
Status: Optional
SUT: ASP/MGC
M3UA_ASP/
M3UA_ASP_RKM/
M3UA_ASP_RKM_I
M3UA_ASP_RKM_I_001 Ensure that the IUT, after sending a REG REQ, upon reception of a message which class is 9 (RKM) and type
is different from 0 ("Reserved"), 1 ("Registration Request"), 2 ("Registration Response"),
3 ("Deregistration Request"), and 4 ("Deregistration Response"), responds with an ERROR message with reason 0x04
("Unsupported Message Type")
ASP marked as ASP-ACTIVE at the SGP
ASP not registered
Reference: RFC4666, ETSI TS 102 381 V1.1.1 (2004-12) Section 3.1.2 [1], Section 3.8.1 [1]
Status: Optional
SUT: ASP/MGC
MISC
M3UA_SGP_ALL_MSGS_MISC2 Test for all different message encoding variations
SUT:
M3UA_4PCO_Test_001 Test 4 PCOs / associations. Requires that appropriate Start test be run first
SUT: SGP
MISC/
MISC_TOYO
toyo_ISUP_1_1_Iriko SG1 is simulated.
SG1 is simulated.
toyo_ISUP_1_1_Iriko_debugger AS is simulated.
AS is simulated.
toyo_ISUP_1_2_Denoko SG2 is simulated.
SG2 is simulated.
toyo_ISUP_1_2_Denoko_debugger AS is simulated.
AS is simulated.
toyo_ISUP_1_3_Irideko SG1 and SG2 are simulated.
SG1 and SG2 are simulated.
toyo_ISUP_1_3_Irideko_debugger AS is simulated.
AS is simulated.
toyo_ISUP_1_4_Irideko SG1 is simulated.
SG1 is simulated.
toyo_ISUP_1_4_Irideko_debugger AS is simulated.
AS is simulated.
toyo_ISUP_1_5_Irideko SG1 is simulated.
SG1 is simulated.
toyo_ISUP_1_5_Irideko_debugger AS is simulated.
AS is simulated.
toyo_ISUP_3_1_Iriko SG1 is simulated.
SG1 is simulated.
toyo_ISUP_3_1_Iriko_debugger AS is simulated.
AS is simulated.
MISC/
MISC_ASP
M3UA_ASP_SSNM_3_1_1 To check that if SSNM message is received at the ASP then it
is reported to the ULP.
ASP and ASP is Active. Also arrange the data in SGP such that DUNA,
DAVA, DUPU, DRST and SCON messages are sent from the SGP to the ASP
with valid parameters and they are sent on stream number 0.
SUT: ASP/MGC
M3UA_ASP_SSNM_3_1_2 To check that if SSNM message is received at the ASP then it
is reported to the ULP.
ASP and ASP is Active. Also arrange the data in SGP such that DUNA,
DAVA, DUPU, DRST and SCON messages are sent from the SGP to the ASP
with valid parameters and they are sent on stream number 0.
SUT: ASP/MGC
M3UA_ASP_SSNM_3_1_3 To check that if SSNM message is received at the ASP then it
is reported to the ULP.
ASP and ASP is Active. Also arrange the data in SGP such that DUNA,
DAVA, DUPU, DRST and SCON messages are sent from the SGP to the ASP
with valid parameters and they are sent on stream number 0.
SUT: ASP/MGC
M3UA_ASP_Traffic_001 Prepare for traffic
Status: Optional
SUT: ASP/MGC
M3UA_ASP_Unblock_001 Prepare for traffic. Send UBL. Use variables
Status: Optional
SUT: ASP/MGC
M3UA_ASP_Unblock_002 Prepare for traffic. Send UBL. Hard-coded
Status: Optional
SUT: ASP/MGC
M3UA_ASP_Unblock_003 Prepare for traffic. Wait for UBL, send UBA
Status: Optional
SUT: ASP/MGC
MISC/
MISC_SGP
M3UA_SGP_Unblock_001 Prepare for traffic. Send UBL
Status: Optional
SUT: SGP
M3UA_SGP_Unblock_002 Prepare for traffic. Wait for UBL, send UBA
Status: Optional
SUT: ASP/MGC
ASPUP To Send ASP-UP Message to SG
To Send ASP-UP Message to SG
ASPACTIVE To Send ASP ACTIVE message to SG
To Send ASP ACTIVE message to SG
ASPDOWN To Send ASP-DOWN Message to SG
To Send ASP-DOWN Message to SG
ASPINACTIVE
ASPUP_5000 To Send 5s worth of ASP-UP Messages to SG
To Send 5s worth of ASP-UP Messages to SG
M3UA_SGP_DATA_V_001 Ensure that the IUT accepts a valid Payload Data Message
ASPs marked as ASP Active at the SGP
Multiple Routing Keys and Routing Contexts are being used across a common association
SUT: SGP
CISCO_SG
SGP_UP To Send ASP-UP Message to SG
To Send ASP-UP Message to SG
SGP_ACTIVE To Send ASP ACTIVE message to SG
To Send ASP ACTIVE message to SG
SGP_INACTIVE
SGP_DOWN To Send ASP-DOWN Message to SG
To Send ASP-DOWN Message to SG
M3UA_SGP_DATA Send data from one point to another
Reference:
Status:
SUT: SGP
ISUP
M3UA_SGP_ISUP_Call_Flow Full ISUP call-flow
Status:
SUT: SGP
M3UA_Misc_PCO1_Heartbeat_S Send a HEARTBEAT on PCO1
SCTP association should be established
M3UA_Misc_PCO2_Heartbeat_S Send a HEARTBEAT on PCO2
SCTP association should be established
M3UA_Misc_PCO3_Heartbeat_S Send a HEARTBEAT on PCO3
SCTP association should be established
M3UA_Misc_PCO4_Heartbeat_S Send a HEARTBEAT on PCO4
SCTP association should be established
RTests
M3UA_RTest_Proc_PREAMBLE_ASP_AUTOMATED_Need_DOWN Test PREAMBLE_ASP_AUTOMATED for proper operation
Test runs independently of any other settings.
Final result should be PASS.
M3UA_RTest_Proc_PREAMBLE_ASP_AUTOMATED_Need_INACTIVE Test PREAMBLE_ASP_AUTOMATED for proper operation
Test runs independently of any other settings.
Final result should be PASS.
M3UA_RTest_Proc_PREAMBLE_ASP_AUTOMATED_Need_ACTIVE Test PREAMBLE_ASP_AUTOMATED for proper operation
Test runs independently of any other settings.
Final result should be PASS.
M3UA_RTest_Proc_PREAMBLE_ASP_AUTOMATED Test PREAMBLE_ASP_AUTOMATED for proper operation
Test runs independently of any other settings.
Final result should be PASS.
M3UA_RTest_Proc_Notify_Type_Str Test Notify_Type_Str for proper return values
Test runs independently of any other settings.
Final result should be PASS.
M3UA_RTest_Proc_Notify_Info_Str Test Notify_Info_Str for proper return values
Test runs independently of any other settings.
Final result should be PASS.
M3UA_RTest_Heartbeat_S Test for message encoding variations
Test runs against itself; one as SENDER, other as RECEIVER
Start LISTENER as ASP (run M3UA_ASP_Start)
Start SENDER as SG (run M3UA_SG_Start)
That establishes the SCTP association.
Start this test in LISTENER.
Start this test in SENDER.
Final result should be PASS.
M3UA_RTest_Heartbeat_Ack_S Test for all different message encoding variations
Test runs against itself; one as SENDER, other as RECEIVER
Start LISTENER as ASP (run M3UA_ASP_Start)
Start SENDER as SG (run M3UA_SG_Start)
That establishes the SCTP association.
Start this test in LISTENER.
Start this test in SENDER.
Final result should be PASS.
M3UA_RTest_Duna_S Test for all different message encoding variations
Test runs against itself; one as SENDER, other as RECEIVER
Start LISTENER as ASP (run M3UA_ASP_Start)
Start SENDER as SG (run M3UA_SG_Start)
That establishes the SCTP association.
Start this test in LISTENER.
Start this test in SENDER.
Final result should be PASS.
M3UA_RTest_Dava_S Test for all different message encoding variations
Test runs against itself; one as SENDER, other as RECEIVER
Start LISTENER as ASP (run M3UA_ASP_Start)
Start SENDER as SG (run M3UA_SG_Start)
That establishes the SCTP association.
Start this test in LISTENER.
Start this test in SENDER.
Final result should be PASS.
M3UA_RTest_Scon_S Test for all different message encoding variations
Test runs against itself; one as SENDER, other as RECEIVER
Start LISTENER as ASP (run M3UA_ASP_Start)
Start SENDER as SG (run M3UA_SG_Start)
That establishes the SCTP association.
Start this test in LISTENER.
Start this test in SENDER.
Final result should be PASS.
M3UA_RTest_Dupu_S Test for all different message encoding variations
Test runs against itself; one as SENDER, other as RECEIVER
Start LISTENER as ASP (run M3UA_ASP_Start)
Start SENDER as SG (run M3UA_SG_Start)
That establishes the SCTP association.
Start this test in LISTENER.
Start this test in SENDER.
Final result should be PASS.
M3UA_RTest_Daud_S Test for all different message encoding variations
Test runs against itself; one as SENDER, other as RECEIVER
Start LISTENER as ASP (run M3UA_ASP_Start)
Start SENDER as SG (run M3UA_SG_Start)
That establishes the SCTP association.
Start this test in LISTENER.
Start this test in SENDER.
Final result should be PASS.
M3UA_RTest_Drst_S Test for all different message encoding variations
Test runs against itself; one as SENDER, other as RECEIVER
Start LISTENER as ASP (run M3UA_ASP_Start)
Start SENDER as SG (run M3UA_SG_Start)
That establishes the SCTP association.
Start this test in LISTENER.
Start this test in SENDER.
Final result should be PASS.

Variable Default Value Description
N_Adaptors 1 Number of adaptors to use. Default = 1
N_Sockets 1 Number of SCTP sockets/associations. Default = 1
ASP_Automated_Preamble FALSE If TRUE, automates test preamble for required test state
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)
Layer_3_Protocol Use_IPv4 Network layer; above Ethernet, default = Use_IPv4
PX_ASP_Preamble_Wait_For_ASP_DOWN TRUE Set to FALSE to bypass ASP_DOWN preamble
Process_Type (null) Role of the Tester: SG or ASP/MGC
Beat_Data "0102030405" Heartbeat Data
StreamID 0 Stream ID for management messages. Default = 0
Local_RK_Identifier_Invalid 100 Invalid Routing Key ID. Default = 100
N_Output_Streams 2 Number of Tester SCTP Output streams
N_Input_Streams 2 Number of Tester SCTP Input streams
Encoding_Type (null) SS7 encoding type
Routing_Context_Invalid 9 Invalid Routing Context ID. Default = 9
T_Wait_ASP_Response_VAL 30000 Time to wait for response
T_Wait_ASP_Ack_VAL 2000 Time to wait for response
Local_RK_Identifier 2 Tester Routing Key ID. Default = 2
Correlation_ID_Used FALSE Use Correlation ID in outgoing messages. Default = FALSE
Correlation_ID 1 Correlation ID to use in outgoing messages
Network_Indicator International Network Indicator. Default = International
Service_Indicator SI_ISUP Service Indicator. Default = SI_ISUP
Orig_PC 50 OPC used in ISUP Data
Dest_PC 4 DPC used in ISUP Data
SLC 0 SLC used in ISUP Data
CIC 1 CIC used in ISUP Data
OPC_Reg '00000032'H OPC used in Registration
DPC_Reg '00000004'H OPC used in Registration
IAM '011000000003060D038090A207011... ISUP IAM Hex
UBL '14'H ISUP UBL Hex
UBA '16'H ISUP UBA Hex
BLO '13'H ISUP BLO Hex
BLA '15'H ISUP BLA Hex
RLC '10'H ISUP RLC Hex
DataStreamID 2 Stream ID for Data. Default = 2
PREAMBLE_ASP_UP_Send_Notify FALSE During ASP preamble, send NOTIFY (AS-INACTIVE) after ASP-UP-ACK? Default = FALSE
ASP_ID_Used TRUE Use ASP ID in outgoing messages? Default = TRUE
ASP_ID 1 ASP ID
Info_Used FALSE Use Info field in outgoing messages? Default = FALSE
Info "Info" Info field value
Traffic_Mode_Used TRUE Use Traffic Mode in outgoing ASPTM messages? Default = TRUE
Traffic_Mode Over_Ride Traffic Mode
Routing_Context_1_Used FALSE Use Routing Context in outgoing ASPTM messages? Default = TRUE
Routing_Context_1 1 Routing Context
Routing_Context_2_Used FALSE Use Routing Context in outgoing ASPTM messages? Default = TRUE
Routing_Context_2 2 Routing Context
Routing_Context_3_Used FALSE Use Routing Context in outgoing ASPTM messages? Default = TRUE
Routing_Context_3 3 Routing Context
Routing_Context_4_Used FALSE Use Routing Context in outgoing ASPTM messages? Default = TRUE
Routing_Context_4 4 Routing Context
Routing_Context_5_Used FALSE Use Routing Context in outgoing ASPTM messages? Default = TRUE
Routing_Context_5 5 Routing Context
Network_Appearance_Used (null) Use Network Appearance in outgoing messages? Default = FALSE
Network_Appearance (null) Network Appearance
Affected_Point_Code_Used (null) Use Affected Point Code in outgoing messages? Default = FALSE
Affected_Point_Code (null) Affected Point Code
M3UA_Orig_PC 4114 OPC used in Misc tests
M3UA_TESTER_PC 8228 Tester OPC used in Misc tests
M3UA_Dest_PC 6171 DPC used in Misc tests
M3UA_Orig_CIC 16640 Orig CIC used in Misc tests
M3UA_Dest_CIC 24832 Dest CIC used in Misc tests
Access_Transport (null) Access transport
Echo_Control_Device ECD_Not_Included Echo Control Device
toyo_repeat_end 5 (null)
toyo_notify_end 5 (null)
toyo_Routing_Context1 11 (null)
toyo_Routing_Context2 12 (null)
toyo_Routing_Context3 13 (null)
toyo_Routing_Context4 14 (null)
toyo_Routing_Context5 15 (null)
toyo_CIC_end 23 (null)
toyo_CIC_start 0 (null)
toyo_OPC1 '000007D1'H (null)
toyo_OPC2 '00000BB9'H (null)
toyo_DPC '000003E8'H (null)
toyo_output_used FALSE (null)
toyo_output_IAM '05000000006501'H (null)
toyo_output_ACM '05000000006506'H (null)
toyo_output_ANM '05000000006509'H (null)
toyo_output_REL '0500000000650C'H (null)
toyo_output_RLC '05000000006510'H (null)
toyo_output_BLO '05000000006513'H (null)
toyo_output_UBL '05000000006514'H (null)
toyo_output_BLA '05000000006515'H (null)
toyo_output_UBA '05000000006516'H (null)
toyo_output_GRS '05000000006517'H (null)
toyo_output_GRA '05000000006529'H (null)
toyo_IAM_data_used FALSE (null)
toyo_IAM_data '00A0001003020B097E10009930111... (null)
toyo_ACM_data_used FALSE (null)
toyo_ACM_data '101401FD0481342000F10800FC05F... (null)
toyo_ANM_data_used FALSE (null)
toyo_ANM_data '011102150400'H (null)
toyo_IAM_Nature_of_connection_indicators '00'H (null)
toyo_IAM_Forward_call_indicators 'A000'H (null)
toyo_IAM_Calling_partys_category '10'H (null)
toyo_IAM_Transmission_midium_requirement '03'H (null)
toyo_IAM_Called_party_number '097E1000993011114444'H (null)
toyo_IAM_Calling_party_number '0A078313431201AAAA'H (null)
toyo_IAM_Ryokin_kuiki_jyoho 'FD0481342000'H (null)
toyo_IAM_Jigyosya_jyoho_tenso 'F10803FB05FE03002143'H (null)
toyo_ACM_Backward_call_indicators '1404'H (null)
toyo_ACM_Ryokin_kuiki_jyoho 'FD0481342000'H (null)
toyo_ACM_Jigyosya_jyoho_tenso 'F10800FC05FE03002143'H (null)
toyo_ANM_Backward_call_indicators '11021504'H (null)
toyo_wait_INIT_VAL 60000 (null)
toyo_wait_ASPUP_VAL 2000 (null)
toyo_wait_ASPAC_VAL 2000 (null)
toyo_wait_IAM_VAL 20000 (null)
toyo_wait_ACM_VAL 1000 (null)
toyo_wait_ANM_VAL 1000 (null)
toyo_wait_REL_VAL 1000 (null)
toyo_wait_RLC_VAL 1000 (null)
toyo_wait_ASPINACTIVE_VAL 5000 (null)
toyo_NOTIFY_Tn_VAL 100 (null)
toyo_IAM_startTn_VAL 4000 (null)
toyo_IAM_Tn_VAL 500 (null)
toyo_ANM_Tn_VAL 3000 (null)
toyo_REL_Tn_VAL 3000 (null)
MyTestSuiteTesterRole (null) Self-test diagnostics
Sender_Response_Wait_Time 4000 Self-test diagnostics
Sender_Pause_Time 1000 Self-test diagnostics
Listener_Wait_Time 30000 Self-test diagnostics

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